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

SSO: Single Signon activity throwing error



User is trying to implement Single Sign-on using PRCustom and SPNEGO. They have configured SPNEGO on tomcat and it is working fine.

When the custom Code-Security authentication activity defined in the AuthService is run, then an exception occurs.

Error Messages

Exception in log file:

Problem executing activity: Code-Security.SSOSampleAuthActivity Invalid request
at com.pega.pegarules.session.internal.mgmt.authentication.Authentication.verifyActivityAccess(
at com.pega.pegarules.session.internal.mgmt.authentication.Authentication.verifyActivityAccess(
at com.pega.pegarules.session.internal.mgmt.authentication.Authentication.setUserSecurityProfile(
at com.pega.pegarules.session.internal.mgmt.authentication.Authentication.setUserSecurityProfile(
at com.pegarules.generated.activity.ra_action_ssosampleauthactivity_2fc7da91d559cf3b23dc42e5dd9bca50.step5_circum0(
at com.pegarules.generated.activity.ra_action_ssosampleauthactivity_2fc7da91d559cf3b23dc42e5dd9bca50.perform(
at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(
at com.pega.pegarules.session.internal.mgmt.authentication.AuthenticationUtil.runActivity(
at com.pega.pegarules.session.internal.mgmt.authentication.SchemePRCustom.authenticateOperator(
at com.pega.pegarules.session.internal.mgmt.authentication.Authentication.doAuthentication(
at com.pega.pegarules.session.internal.engineinterface.service.HttpAPI.handleAuthentication(
at com.pega.pegarules.session.external.engineinterface.service.EngineAPI.activityExecutionProlog(
at com.pega.pegarules.session.external.engineinterface.service.EngineAPI.processRequestInner(
at sun.reflect.GeneratedMethodAccessor78.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(

Steps to Reproduce

Not Applicable

Root Cause

The custom servlet defined in the web.xml is properly set to use PRCustom as the AuthType.

The activity was using PRExternal style authentication and calling setUserSecurityProfile in step 5 of the custom activity.

Since the AuthType is PRCustom the usage of setUserSecurityProfile is not allowed and an exception is thrown.


Update authentication activity to use PRCustom style configuration.

Published April 12, 2018 - 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?

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