Support Article
Error displays is logs when logging in using LDAP authentication
SA-57455
Summary
Error displays in logs during custom authentication when logging in using Lightweight Directory Access Protocol (LDAP) authentication. Issue occurs after upgrading to Pega 7.4 from Pega 7.3.1.
Error Messages
831 [http-nio-8080-exec-3] [ STANDARD] [ ] [] (ngineinterface.service.HttpAPI) ERROR | com.pega.pegarules.pub.PRRuntimeException
com.pega.pegarules.pub.PRRuntimeException: No failure response set by custom authentication activity
at com.pega.pegarules.session.internal.mgmt.authentication.SchemePRCustom.onAuthenticationFailure(SchemePRCustom.java:975) ~[prprivate.jar:?]
at com.pega.pegarules.session.internal.mgmt.authentication.Authentication.doAuthentication(Authentication.java:770) ~[prprivate.jar:?]
at com.pega.pegarules.session.internal.engineinterface.service.HTTPAuthenticationHandler.performAuthentication(HTTPAuthenticationHandler.java:250) ~[prprivate.jar:?]
Steps to Reproduce
- Upgrade from Pega 7.3.1 to Pega 7.4
- Log in with PRWebLDAP2
Root Cause
When user imports user records to the system, they are marked as Force password change on next login and Disable Operator. MODEL_USER record is used when creating new user records during custom authentication. The MODEL_USER record is imported to the system after upgradation to Pega 7.4 as it is associated to a ruleset. Authentication fails when user is creating a new user record using the disabled MODEL_USER record.
Resolution
Perform the following local-change:
Update the MODEL_USER record with the following steps:
- Uncheck Disable Operator
- Click Save
- Uncheck Force password change on next login
- Click Save
Published November 29, 2018 - Updated December 2, 2021
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.