Failed to find a 'RULE-OBJ-ACTIVITY'
Predictive Diagnostic Cloud (PDC) displays an error regarding the single sign-on (SSO) Authentication activity. This occurs on changing the Authentication activity in the Advanced configuration settings from pySAMLWebSSOAuthenticationActivity to CustomSAMLWebSSOAuthenticationActivity.CustomSAMLWebSSOAuthenticationActivity in the Code-Security class and tied to GRPXXX:01-01-01.
Failed to find a 'RULE-OBJ-ACTIVITY' with the name 'CUSTOMSAMLWEBSSOAUTHENTICATIONACTIVITY' that applies to 'Code-Security'. There were 1 rules with this name in the rulebase, but none matched this request. The 1 rules named 'CUSTOMSAMLWEBSSOAUTHENTICATIONACTIVITY' defined in the rulebase are:1 related to applies-to class 'Code-Security', but were defined in rulesets which are not in your rulesetlist: 'GRPXXX:01-01-01'.Current RulesetList:unauthenticated:,Pega-ProcessCommander:07-10,Pega-DeploymentDefaults:07-10,Pega-DecisionScience:07-10,Pega-DecisionArchitect:07-10,Pega-LP-Mobile: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-SystemOperations:07-10,Pega-UpdateManager:07-10,Pega-SecurityVA:07-10,Pega-Feedback:07-10,Pega-AutoTest:07-10,Pega-AppDefinition:07-10,Pega-ImportExport:07-10,Pega-Localization...
Steps to Reproduce
The ruleset in which CustomSAMLWebSSOAuthenticationActivity activity was defined was not referred in the unauthenticated access group mentioned in the browser requestor type.
Perform the following local-change:
- Navigate to Records > Sysadmin > Requestor Type.
- Open the browser requestor type for the system name.
- Check the access group provided.
- Add the ruleset to the access group.
0% found this useful