Bug 50262 - [UDM HTTP API] PATCH position does not move user
Summary: [UDM HTTP API] PATCH position does not move user
Status: RESOLVED WONTFIX
Alias: None
Product: UCS
Classification: Unclassified
Component: UDM - REST API
Version: UCS 4.4
Hardware: Other Linux
: P5 normal
Target Milestone: ---
Assignee: UMC maintainers
QA Contact: UMC maintainers
URL: https://forge.univention.org/bugzilla...
Keywords:
Depends on:
Blocks:
 
Reported: 2019-09-25 16:49 CEST by Daniel Tröder
Modified: 2024-06-27 12:10 CEST (History)
2 users (show)

See Also:
What kind of report is it?: Development Internal
What type of bug is this?: ---
Who will be affected by this bug?: ---
How will those affected feel about the bug?: ---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Customer ID:
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Daniel Tröder univentionstaff 2019-09-25 16:49:15 CEST
When telling the UDM REST API to change the "position" of an object, it only works in PUT, but not in PATCH:

-------------------------------------------------------

$ udm users/user create --set username="newuser01" --set firstname="Random" --set lastname="User" --set password="Univention.99"
WARNING: The object is not going to be created underneath of its default containers.
Object created: uid=newuser01,dc=uni,dc=dtr

-------------------------------------------------------

curl -i -X PATCH \
   -H "Accept:application/json" \
   -H "Content-Type:application/json" \
   -d \
'{
  "position": "cn=users,dc=uni,dc=dtr"
}' \
 'https://m66.uni.dtr/univention/udm/users/user/uid=newuser01,dc=uni,dc=dtr'

-------------------------------------------------------

$ univention-ldapsearch -LLL  uid=newuser01 dn
dn: uid=newuser01,dc=uni,dc=dtr
Comment 1 Jan-Luca Kiok univentionstaff 2024-06-27 12:10:54 CEST
This issue has been filed against UCS 4.4.

UCS 4.4 is out of general maintenance and components may have vastly changed in later releases. Thus, this issue is now being closed.

If this issue still occurs in newer versions, please use "Clone this bug" or reopen this issue. In this case please provide detailed information on how this issue is affecting you.