Ask Questions and Find Answers

Thanks for your reposne Zsigmond! Yes, "ldap.auth.enabled" property is set as true. The cutomer recently migated to new LDAP server, its corbon copy of earlier versoin of LDAP. Facing this issue post LDAP server migration. We cleared below cache from Liferay "Server Administration" page arleady

Clear content cached by this VM.
Clear content cached across the cluster.
Clear the database cache.
Clear the direct servlet cache.

Please suggest us if we need to clean any other cache in the portlet framework or give some more pointer to find out an actual cause for the failure

Thanks

SATHISH

Hi Sathish,

Unfortunately, the only think I could do is to try to find the problem with debugging. Without that I have no idea why it is not working.

From the lines around which I linked earlier it seems clear that the message may come only, if the PropsValues.LDAP_AUTH_ENABLED is false: https://github.com/liferay/liferay-portal/blob/6.2.x/portal-impl/src/com/liferay/portal/security/auth/AuthSettingsUtil.java#L59-L64, unless there is some customization around.

Regards,
Zsigmond

Yes Zsigmond we had enabled the debug and analyzing the logs. 

Do you have a flowchart/doc refernece which explains the liferay -  LDAP authentication fuctionality ?

Thanks

Sathish

Hi Sathish,

Unfortunately, there is no such flowchart/doc. The only thing I also could do is to debug the class above and the https://github.com/liferay/liferay-portal/blob/6.2.x/portal-impl/src/com/liferay/portal/security/auth/LDAPAuth.java#L363-L369 lines to see why the property is false. Have you tried that already?

Zsigmond

Hi Zsigmond

Thanks for your time!

Yes, we debugged further and found that the issue with LDAP sync. The custom LDAP attribute "modifyTimestamp" was not updated properly. Did the changes in the LDAP server and its worked.  

Thanks lot for your support!

Thanks

Sathish

Great to hear!

Zsigmond