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

Mashup Code Session Issue

SA-40148

Summary



Requirement is launching Pega portal from Salesforce and this is achieved via mashup code.
In Internet Explorer, logging in as User A in Pega portal in one of the tab logged in as User B in Salesforce and trying to launch Pega portal and instead of getting User B, User A is displayed.
Pega is taking the old session ID, that is, User A.


Error Messages



Not Applicable


Steps to Reproduce



Not Applicable


Root Cause



An issue with the mashup code session.

Resolution



Here’s the explanation for the reported behavior:

If salesforce application which is launched in other tab, also uses same server and authentication type as User A , ideally login screen will not be prompted, as cookie gets shared between two tabs opened in the browser.

In generic, from same browser session, one cannot open two different user sessions requesting a single server.

Hence this is an expected behavior.

Published December 6, 2017 - 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