Error when saving user if objectClass person is missing.
Error when saving user if objectClass person is missing.
Hi!
When editing some existing users I receive this error message after saving the entry:
Error Error when saving There is already an entry with the same dn : uid=username,ou=people,ou=dept,dc=example,dc=com
The log shows: wwwsrv apache2: FusionDirectory [fd-admin]: (create) uid=username,ou=people,ou=dept,dc=example,dc=com of type plugin/user objectC wwwsrv apache2: FusionDirectory [fd-admin]: (modify) uid=username,ou=people,ou=dept,dc=example,dc=com of type plugin/posixAccount wwwsrv apache2: FusionDirectory [fd-admin]: (modify) uid=username,ou=people,ou=dept,dc=example,dc=com of type plugin/mailAccount wwwsrv apache2: FusionDirectory [fd-admin]: (modify) uid=username,ou=people,ou=dept,dc=example,dc=com of type plugin/ppolicyAccou
The changes are saved successfully. The error show up with subsequent edits of the same user. Not all users are affected. All users were imported from an existing directory during installation of fusiondirectory.
The difference between user entries with and without this error is the objectClass person. The error occurs when objectClass person is missing.
After adding the objectClass person manually, the error is gone.
Christian
(from redmine: issue id 4746, created on 2016-04-22, closed on 2016-04-28)
- Changesets:
- Revision c4d85826 by Côme Chilliet on 2016-04-27T05:51:11.000Z:
Fixes #4746 The is_this_account user method is now more permissive (only inetOrgPerson is needed)- Revision a77f7c58 by Côme Chilliet on 2016-04-27T05:52:51.000Z:
Fixes #4746 The is_this_account user method is now more permissive (only inetOrgPerson is needed)- Custom Fields:
- Bug in version: 1.0.11
Activity
Hi!
Most users had inetOrgPerson, organizationalPerson, posixAccount, shadowAccount, gosaMailAccount and person. Some users however had the object class person missing and then the error occurred.
I suppose fusiondirectory did not check or add objectclass person during the migration of users from the existing DIT.
(from redmine: written on 2016-04-26)
By ckreidl on 2017-09-02T15:28:19 (imported from GitLab)
I really hate the way LDAP handle objectClasses… organizationalPerson extends person class, so your users match the filter objectClass=person, but when we get the objectClass list person is not in it :-/
Can you try what I pushed see if it’s better? I’ve changed the method checking if a user main tab was existing to only check inetOrgPerson.
(from redmine: written on 2016-04-27)
By Côme Chilliet on 2017-09-02T15:28:19 (imported from GitLab)
added Changed label
By bmortier on 2018-10-04T20:00:59 (imported from GitLab)
