Submit Feedback
Legacy Knowledge Base
Published Jul. 2, 2025

Updated Email Addresses in LDAP are not Imported to Liferay DXP 7.0

Written By

Justin Choi

How To articles are not official guidelines or officially supporteddocumentation. They are community-contributed content and may not alwaysreflect the latest updates to Liferay DXP. We welcome your feedback toimprove How to articles!

While we make every effort to ensure this Knowledge Base is accurate, itmay not always reflect the most recent updates or official guidelines.We appreciate your understanding and encourage you to reach out with anyfeedback or concerns.

Legacy Article

You are viewing an article from our legacy "FastTrack"publication program, made available for informational purposes. Articlesin this program were published without a requirement for independentediting or verification and are provided "as is" withoutguarantee.

Before using any information from this article, independently verify itssuitability for your situation and project.

Issue

This article documents a product limitation and a possible workaround for importing a user whose email address was updated in LDAP into a Liferay DXP instance.

Environment

  • Liferay DXP 
  • LDAP server

Resolution

  • This is actually a limitation and intended behavior. By default, Liferay Portal and DXP uses email addresses to authenticate a user. Therefore, a Liferay instance prohibits an updated user's email address in LDAP from being imported to Liferay when it is also being used to authenticate the user in Liferay. Otherwise, it throws an error in the console log and the import fails.
  • One potential workaround is to change the method of authenticating users from email address to screen name, you could update user email addresses and have the updates imported to Liferay DXP. (While this configuration is in effect, the screen name cannot be modified.) When the import has finished, change the method of authentication back to email address if desired.

Additional Information

  • LPS-34720 has been created as a feature request.
Did this article resolve your issue ?
Legacy Knowledge Base
Did this article resolve your issue ?