Univention Bugzilla – Bug 49760
appcenter IDM notifications (Push) missing "old" data
Last modified: 2020-11-16 10:18:53 CET
When a user is deleted from LDAP, the apps listener script dumps a JSON file into the container that does not contain the data from the "old" dictionary. It has only: { "dn": "uid=un2,cn=users,dc=uni,dc=dtr", "id": "4d1ce39c-2df0-1039-903f-23c4e2dbff04", "object": null, "options": null, "udm_object_type": "users/user" } There are scenarios where that is not enough. For example if the ID of/in a foreign system is stored in the user object, connecting to it won't be possible, because the data is missing in the JSON file.
The id of the object is "id": "4d1ce39c-2df0-1039-903f-23c4e2dbff04", please store this on the foreign system, to identify deleted objects. We omitted "old data" on purpose.
Yes, doing it. If you want, you can close this with wontfix.
For various apps it has become a necessity to keep various other data (not just the ID) of the previous state of an LDAP object in a database, because the 'old' data is not passed. This is an unnecessary burden for the app development and produces a duplication of code in each app (loading and storing data in a database). For example, the ucsschool-id-connector app requires: * for its group "listener": users: List[str] * for its user "listener": schools: List[str] record_uid: str source_uid: str
That data is not (only) required for the "delete" operation, but more often for the "modify" and "move" operations.