-
Type:
Bug
-
Status: Closed
-
Priority:
Minor
-
Resolution: Fixed
-
Affects Version/s: 5.1.1
-
Fix Version/s: 5.1.2
-
Component/s: None
-
Labels:None
LDAP Export - User is exported before Contact is created
Exporting to LDAP is trigger by 2 listeners. UserListener and ContactListener.
Currently, after a user or contact is updated or created, Liferay will try to export the User/Contact to LDAP (if this feature is turned on). However, this is a problem because the User is created before the Contact is created. So after the User is created.. and before the Contact is created, Liferay will try and export the LDAPUser. But the LDAPUser has information like "firstName" and "lastName".. fields which are populated with data that comes from the Contact.. again, which hasnt been created yet.
This results in a LDAPUser being exported to LDAP with "" (empty string) values being passed to the LDAP server. Some LDAP servers will let it slide. That is why currently in Liferay 5.1.1, the export functionality still works with apacheDS.. however some LDAP servers will choke on this and will refuse to accept the incomplete User.
The fix is to simply remove the code which triggers the export after the user is created.. and depend on the code that triggers the export after the contact is created.
Scott
- duplicates
-
LEP-5671 Create user fails if LDAP Export is enabled
-
- Closed
-
-
LEP-4898 When a new account is created via "Createhttp://www.liferay.com/web/guest/community/forums/message_boards/message/418603 Account" and LDAP error 21 occurs because firstName and lastName are NULL
-
- Closed
-
- is duplicated by
-
LPS-1627 Problem with LDAP integration (Liefray 5.1.2 )::::[LDAP: error code 21 - givenName: value #0 invalid per syntax]
- Closed
-
LEP-4605 LDAP Export throwing Exceptions and not retrying
-
- Closed
-
- relates
-
LEP-7727 Automatic population of database fails if ldap export is on
-
- Closed
-
-
LPS-2755 LDAP export fails when importing a user from LDAP
- Closed