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

UserRole does not updated on the OperatorID page



While accessing a Pega Platform application session via an iFrame embedded in an external application, users see that if they end their current session and attempt to log in using a different role, without starting a new browser session, they are still accessing the initial Pega Platform application session. 

Error Messages

No error messages are displayed.

Steps to Reproduce

  1. Log in with a specific role from the external application.
  2. End the current Pega Platform application session.
  3. Log in again with a different user role but with same user id in the same browser session.

Root Cause

An issue in the custom application code or rules resulted in the initial Pega Platform application session's requestor not being unauthenticated and removed.


Here’s the explanation for the reported behavior: If the same browser session is to be used, the original application session's requestor must be unauthenticated, otherwise the same application session is reused.

Published August 31, 2015 - 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