Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Error displays is logs when logging in using LDAP authentication



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 | No failure response set by custom authentication activity
at com.pega.pegarules.session.internal.mgmt.authentication.SchemePRCustom.onAuthenticationFailure( ~[prprivate.jar:?]
at com.pega.pegarules.session.internal.mgmt.authentication.Authentication.doAuthentication( ~[prprivate.jar:?]
at com.pega.pegarules.session.internal.engineinterface.service.HTTPAuthenticationHandler.performAuthentication( ~[prprivate.jar:?]

Steps to Reproduce

  1. Upgrade from Pega 7.3.1 to Pega 7.4
  2. 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.    


Perform the following local-change:
Update the MODEL_USER record with the following steps:
  1. Uncheck Disable Operator
  2. Click Save
  3. Uncheck Force password change on next login
  4. Click Save

Published November 29, 2018 - Updated December 2, 2021

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us