Question
Cognizant Technology Solutions
US
Last activity: 8 Sep 2016 16:49 EDT
Unauthenticated or not available error with Pega LDAP Url
We have 5 different Pega LDAP urls. LDAP1 and LDAP2 are not working. LDAP3 and LDAP4 and LDAP5 urls are working fine. We are gettting the below error in logs while accessing LDAP1 and LDAP2 urls.
Login screen error:
Status fail
Message There has been an issue; please consult your system administrator
Operator ID Unauthenticated or not available
Requestor ID HA2A751F818D9FED213F4F7EF4B957C5A
Timestamp Wed Sep 07 11:58:43 EDT 2016
Engine Version PegaRULES 7.10 ML8 (coreAssemblyCached_718_675)
Pega Log errors:
"Caused by: com.pega.pegarules.pub.generator.RuleNotFoundException: Failed to find a 'RULE-OBJ-ACTIVITY' with the name 'XXXLDAPAUTHENTICATION' that applies to 'Code-Security'. There were 4 rules with this name in the rulebase, but none matched this request. The 4 rules named 'XXXLDAPAUTHENTICATION' defined in the rulebase are:
4 related to applies-to class 'Code-Security', but were defined in rulesets which are not in your rulesetlist: {ABCFW:02-03-02, ABCFW:02-03-01, ABCFW:02-02-01, ABCFW:02-01-01}.
We have 5 different Pega LDAP urls. LDAP1 and LDAP2 are not working. LDAP3 and LDAP4 and LDAP5 urls are working fine. We are gettting the below error in logs while accessing LDAP1 and LDAP2 urls.
Login screen error:
Status fail
Message There has been an issue; please consult your system administrator
Operator ID Unauthenticated or not available
Requestor ID HA2A751F818D9FED213F4F7EF4B957C5A
Timestamp Wed Sep 07 11:58:43 EDT 2016
Engine Version PegaRULES 7.10 ML8 (coreAssemblyCached_718_675)
Pega Log errors:
"Caused by: com.pega.pegarules.pub.generator.RuleNotFoundException: Failed to find a 'RULE-OBJ-ACTIVITY' with the name 'XXXLDAPAUTHENTICATION' that applies to 'Code-Security'. There were 4 rules with this name in the rulebase, but none matched this request. The 4 rules named 'XXXLDAPAUTHENTICATION' defined in the rulebase are:
4 related to applies-to class 'Code-Security', but were defined in rulesets which are not in your rulesetlist: {ABCFW:02-03-02, ABCFW:02-03-01, ABCFW:02-02-01, ABCFW:02-01-01}.
Current RulesetList:
Pega-ProcessCommander:07-10,
Pega-LP-ProcessAndRules:07-10,
Pega-LP-Integration:07-10,
Pega-LP-Reports:07-10,
Pega-LP-SystemSettings:07-10,
Pega-LP-UserInterface:07-10,
Pega-LP-OrgAndSecurity:07-10,
Pega-LP-DataModel:07-10,
Pega-LP-Application:07-10,
Pega-LP:07-10,
Pega-UpdateManager:07-10,
Pega-SecurityVA:07-10,
Pega-Feedback:07-10,
Pega-AutoTest:07-10,
Pega-A...........
***Updated by Moderator: Vidyaranjan| Included Categories***
Pegasystems Inc.
US
What is the top-level exception with this "caused by"? Provide the full stack trace if possible.
Also, your "current ruleset list" is cutoff before we see what Major version of "ABCFW" you are under. I suspect you may be in 03 and will need to skim.
Pegasystems Inc.
US
Looks like the problem is that the activity you have setup for you Authentication Service is not available to unauthenticated users.
The activity "XXXLDAPAUTHENTICATION" has to be in a RuleSet that is defined in the AccessGroup that is defined in the Requestor Type Browser instance for the system name.
For example, my system name is prpc718. (This doesn't change per verison of PRPC)
So I would bring up the prpc718 BROWSER instance. (See screen shot below)
I have an AccessGroup specified here of SSOAuth:Unauthenticated. This uses an SSOAuth Application that has one RuleSet Defined: SSOAuth:01-XX-XX. The SSOAUth application becomes what unauthenticated users have access to. I would not just access to an entire application. All I have in this RuleSet is simply 10 years worth of testing authentication activties .
You just need to make sure you activities used for authentication are defined in a RuleSet available to unauthenticated users.
Looks like the problem is that the activity you have setup for you Authentication Service is not available to unauthenticated users.
The activity "XXXLDAPAUTHENTICATION" has to be in a RuleSet that is defined in the AccessGroup that is defined in the Requestor Type Browser instance for the system name.
For example, my system name is prpc718. (This doesn't change per verison of PRPC)
So I would bring up the prpc718 BROWSER instance. (See screen shot below)
I have an AccessGroup specified here of SSOAuth:Unauthenticated. This uses an SSOAuth Application that has one RuleSet Defined: SSOAuth:01-XX-XX. The SSOAUth application becomes what unauthenticated users have access to. I would not just access to an entire application. All I have in this RuleSet is simply 10 years worth of testing authentication activties .
You just need to make sure you activities used for authentication are defined in a RuleSet available to unauthenticated users.
Cognizant Technology Solutions
US
Thank you for the response.
My custom athentication activity is setup for Authentication Service is available to unauthenticated accessgroup. The Browser requestor type is using unauthenticated accessgroup, which is configured with our application ruleset stack which has custom authentication activities. We cleaned up rule cache and deleted pega temp folder before restart. But it did not resolve the issue. As mentioned earlier, other LDAP urls LDAP3, LDAP4 and LDAP5 are working fine. Looks like LDAP1 and LDAP2 setting are messed up. Are there are backend tables still referring the wrong accessgroup which has pega product ruleset stack? Do we need to cleanup any tables?