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

NullPointerException when login using SSO



Whenever user logs in using SSO URL, the system throws NullPointerException.

Error Messages

Status fail
Message caught exception java.lang.NullPointerException
Requestor ID H87CF40994983A6794F981C39FDF3A0D7
Timestamp Mon Oct 27 13:30:58 EDT 2014
Engine Version PegaRULES 7.10 ML5 (coreAssemblyCached_715_230)

Root Cause

Any obj-save to any page within the AuthService login activity triggers a Rule-Declare-Trigger for Data-Admin-Operator-ID. The page class is NOT Data-Admin-Operator-ID yet it is firing.
This is causing issue when launching a secondary thread. The OperatorID page is blank and the “myStepPage” in ApplicationSetup step 2 is null.


Removing Obj-Save of Operator ID in SSO Activity solved the issue. Users should never save the operator record from within the authentication activity. It’s saved when the activity ends and the engine takes back control.

Published January 31, 2016 - 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