Hide Forgot
Help Desk Ticket Reference: https://na7.salesforce.com/500A0000004TFsI Workaround Description: disable connection pooling - com.sun.jndi.ldap.connect.pool=false project_key: JBEPP Use case: I created a user named testuser3 with password "testuser3" in EPP Classic portal. I can successfully login with the testuser3 username and password. Then, I change the user password from "testuser3" to "other". After that, I logout. When I login using user testuser3 and password "testuser3", I can still login. Also, when I login using the new password "other", I can login as well. The problem is gone after I restart the EPP, i.e. I can only login using the new password "other".
Release Notes Docs Status: Removed: Not Yet Documented Added: Documented as Known Issue Release Notes Text: Added: An issue has been reported about EPP caching recently changed passwords. After a user changes their password, both the old and new password will allow them to log into the portal. This situation persists until the portal is restarted.
Workaround is to disable LDAP connection pooling. This is fixed in PLIDM 1.1.7.CR01 and the case can be closed once picketlink idm version is upgraded.
Link: Added: This issue is related to JBEPP-620
Release Notes Docs Status: Removed: Documented as Known Issue Added: Documented as Resolved Issue
Link: Added: This issue depends JBEPP-621
Link: Added: This issue depends JBEPP-622