LDAP and password change question

[Ben Davis, geändert vor 16 Jahren.]

I have my portal server configured so that LDAP is enabled but not required. What is supposed to happen when an existing user changes their Active Directory password?

I have two users who changed their passwords. One is able to login to Liferay with her new password but the other person still has to use her old one. Any ideas why? Is there a way other than to delete the account to fix this?

[Tobias Amon, geändert vor 16 Jahren.]

Hi,

as far as I know LDAP is used as "failover" database (when required not activated) when a user logs in. If the internal password fails liferay will try to authenticate against LDAP.

That means when you change your ldap password you should be able to use the new one. But I also had some issues when changing password in LDAP. maybe thats a bug.

[Ben Davis, geändert vor 16 Jahren.]

Thanks for the reply. I think you're right. I looked at the User_ table and the only difference between the accounts was the PasswordModifiedDate field was NULL for the account that was not working. I set the user's password to some random text and now she can login using her current AD password.

[Ramesh Radhakrishnan, geändert vor 15 Jahren.]

How do we synchronize the password in open ldap when a user changes the password in liferay?

[Vahid m, geändert vor 15 Jahren.]

Hi all,

password updates in Active Directory through LDAP should be made by TLS or SSL and
password should be in Byte[] check below

http://forums.sun.com/thread.jspa?threadID=581425&tstart=50
http://forums.sun.com/thread.jspa?threadID=592611
http://forum.java.sun.com/thread.jspa?threadID=581425&tstart=15



Cheers

[Scott Dorcas, geändert vor 13 Jahren.]

Ben - I realize this is an old post, but did you ever find a permanent solution? I have a customer on Liferay 4.2.2 experiencing the exact issue as you did.

Many thanks.

[Ben Davis, geändert vor 13 Jahren.]

I never did figure out what the real cause was before we upgraded and the problem went away.
If I remember correctly, deleting the account and then have the user login and auto-create a new account always fixed the problem.