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

WEBLDAP1 auth service cannot find application rulesets

SA-16523

Summary



When the URL for WEBLDAP1 is opened, an error occurs and the user is unable to reach the login screen.
Server.log shows an error indicating that the Data-Admin-AuthService WEBLDAP1 cannot find the login activity.


Error Messages



Problem executing activity: Code-Security.<LOGIN_ACTIVITY>… Failed to find a 'RULE-OBJ-ACTIVITY' with the name '<LOGIN_ACTIVITY>' that applies to 'Code-Security'. There were rules with this name in the rulebase, but… [it is] defined in rulesets which are not in your rulesetlist: <RULESET_NAME_OF_ACTIVTY>:<RULESET_VERSION_OF_ACTIVITY>.

In the browser:

Status fail
Message There has been an issue; please consult your system administrator
Operator ID Unauthenticated or not available
Requestor ID H99423F501E07D9FDADE4B6E78460000A
Timestamp Thu Oct 29 16:19:27 CDT 2015
Engine Version PegaRULES 7.10 ML8 (coreAssemblyCached_718_675)


Steps to Reproduce



Open http://<PRPC_HOST>:8080/prweb/PRWebLDAP1 in a browser.


Root Cause



The Data-Admin-Requestor <SystemName>  Browser instance was not specifying the correct AccessGroup that had defined the RuleSet that the Login Activity lives in. 
 

Resolution



Change the Data-Admin-Requestor <SystemName> browser instance to use an AccessGroup that specifies the correct RuleSet for the custom SSO Login Activity.

Published January 8, 2016 - Updated October 8, 2020

Was this useful?

100% 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