We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
How do we want to handle Entry Already Exists errors for ldap_object_attributes?
Entry Already Exists
Error: LDAP Result Code 68 "Entry Already Exists": 00000562: UpdErr: DSID-031A11C4, problem 6005 (ENTRY_EXISTS), data 0
In my case, a member is already in the group.
One one hand, it'd be nice if the provider "absorbed" duplicates, ignored the error, and then took ownership of that attribute.
On the other hand, maybe that'd be a strange and unexpected behavior... Perhaps we add inherit_duplicates flag?
inherit_duplicates
The text was updated successfully, but these errors were encountered:
No branches or pull requests
How do we want to handle
Entry Already Existserrors for ldap_object_attributes?Error: LDAP Result Code 68 "Entry Already Exists": 00000562: UpdErr: DSID-031A11C4, problem 6005 (ENTRY_EXISTS), data 0In my case, a member is already in the group.
One one hand, it'd be nice if the provider "absorbed" duplicates, ignored the error, and then took ownership of that attribute.
On the other hand, maybe that'd be a strange and unexpected behavior... Perhaps we add
inherit_duplicatesflag?The text was updated successfully, but these errors were encountered: