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

Failed to find a 'RULE-OBJ-ACTIVITY'

SA-76446

Summary



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.


Error Messages



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



Not Applicable


Root Cause



The ruleset in which CustomSAMLWebSSOAuthenticationActivity activity was defined was not referred in the unauthenticated access group mentioned in the browser requestor type.


Resolution



Perform the following  local-change:
  1. Navigate to Records > Sysadmin > Requestor Type.
  2. Open the browser requestor type for the system name.
  3. Check the access group provided.
  4. Add the ruleset to the access group.

Published April 2, 2019 - Updated October 8, 2020

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?

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