-
-
Notifications
You must be signed in to change notification settings - Fork 9.6k
[LDAP] Update throws "Constraint violation" #21328
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
@csarrazi Can you have a look here? |
@estahn can you try adding the This is probably a limitation due to your LDAP server only letting you edit a limited set of attributes. It is not a bug from the component, but rather a limitation due to server configuration. This should be fixed once a better implementation of #21856 will be implemented (I suggested an implementation in the related PR). |
ping @estahn :) |
Sorry for the late response. I will have a look this week. |
Closing for now due to the lack of a reproducer. Please leave a comment with more information and we can consider to reopen. |
update dosen't work. I have the same Error (Constraint violation). updating the entry with mod_replace works with following code:
|
@Sonny333Black Are you able to provide a small reproducer? |
@xabbuh because by some attributes I don't have the premission |
+1 |
Using Microsoft Active Directory. Not working example :
Working example:
|
To give some feedback on this, the original intent for the component was to implement a change manager for the LDAP entries. E.g. being able to do |
When fetching an entry from the ActiveDirectory server and then immediately saving it again, we see the following error:
If using only certain attributes, e.g.
It will succeed.
So pushing the entire LDAP entry to be updated is not working or will not always work.
The text was updated successfully, but these errors were encountered: