Bug 31317 - Removing users may lead to inconsistencies in secretary attribute
Removing users may lead to inconsistencies in secretary attribute
Status: REOPENED
Product: UCS
Classification: Unclassified
Component: UMC - Users
UCS 5.0
Other Linux
: P5 normal (vote)
: UCS 3.2-x
Assigned To: UMC maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-05-08 14:32 CEST by Sönke Schwardt-Krummrich
Modified: 2020-07-03 22:57 CEST (History)
4 users (show)

See Also:
What kind of report is it?: ---
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):
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Sönke Schwardt-Krummrich univentionstaff 2013-05-08 14:32:50 CEST
During removal of user objects the UDM does not check if the "secretary" LDAP attributes of a user refers to the to be deleted user object. After removing the user object this lead e.g. to crashes in third party software.

root@master10:~# eval "$(ucr shell)"; udm users/user create --position "cn=users,$ldap_base" --set lastname="Testuser" --set username="testuser" --set password="univention"
Object created: uid=testuser,cn=users,dc=nstx,dc=local

root@master10:~# udm users/user create --position "cn=users,$ldap_base" --set lastname="Testuser2" --set username="testuser2" --set password="univention" --set secretary=uid=testuser,cn=users,dc=nstx,dc=local
Object created: uid=testuser2,cn=users,dc=nstx,dc=local

root@master10:~# udm users/user remove --dn uid=testuser,cn=users,dc=nstx,dc=local
Object removed: uid=testuser,cn=users,dc=nstx,dc=local

root@master10:~#  univention-ldapsearch -xLLL uid=testuser2 secretary
dn: uid=testuser2,cn=users,dc=nstx,dc=local
secretary: uid=testuser,cn=users,dc=nstx,dc=local

root@master10:~#
Comment 1 Stefan Gohmann univentionstaff 2017-06-16 20:38:07 CEST
This issue has been filed against UCS 3. UCS 3 is out of the normal maintenance and many UCS components have vastly changed in UCS 4.

If this issue is still valid, please change the version to a newer UCS version otherwise this issue will be automatically closed in the next weeks.
Comment 2 Sven Anders 2018-06-06 14:56:02 CEST
Affects UCS 4.2

root@vm-ucsfresh42:~#  eval "$(ucr shell)"; udm users/user create --position "cn=users,$ldap_base" --set lastname="Testuser" --set username="testuser" --set password="univention"
Object created: uid=testuser,cn=users,dc=ham,dc=digitec,dc=de
root@vm-ucsfresh42:~# udm users/user create --position "cn=users,$ldap_base" --set lastname="Testuser2" --set username="testuser2" --set password="univention" --set secretary=uid=testuser,cn=users,dc=nstx,dc=local
Object created: uid=testuser2,cn=users,dc=ham,dc=digitec,dc=de
root@vm-ucsfresh42:~#  udm users/user remove --dn uid=testuser,cn=users,dc=nstx,dc=local
E: object not found
root@vm-ucsfresh42:~# udm users/user remove --dn uid=testuser,cn=users,$ldap_base
Object removed: uid=testuser,cn=users,dc=ham,dc=digitec,dc=de
root@vm-ucsfresh42:~# univention-ldapsearch -xLLL uid=testuser2 secretary
dn: uid=testuser2,cn=users,dc=ham,dc=digitec,dc=de
secretary: uid=testuser,cn=users,dc=nstx,dc=local
Comment 3 Florian Best univentionstaff 2019-03-11 21:12:04 CET
Best would be to fix this via Bug #48956.
Comment 4 Florian Best univentionstaff 2019-03-11 21:21:21 CET
I added a - currently skipped - test case: 61_udm-users/40_secretary_reference_update
It checks all 5 possible combinations:
* rename / modrdn of object
* removal of object
* move of object
* rename of container containing object
* move of container containing object
Comment 5 Ingo Steuwer univentionstaff 2020-07-03 20:55:26 CEST
This issue has been filed against UCS 4.2.

UCS 4.2 is out of maintenance and many UCS components have changed in later releases. Thus, this issue is now being closed.

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