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

IAC : same requestor used for different user in same browser

SA-24669

Summary



The user has a web Mash up portal in which pega application screens are displayed. When a user logs in to the parent portal and opens a pega case in portal a thread is created for the logged in user in pega. After the user finishes their work, the user logs off parent portal. Now when another user logs in to the portal and tries to open a pega case, then an error is thrown:

"you are not authorized work on this case".

User observed that pega is trying to use the existing requestor even though the New USER credentials are passed as part of the request. Due to this above error is being thrown.


Error Messages



You are not authorized to perform this assignment.


Steps to Reproduce

  1. Create a Parent Portal and include a component to display pega cases.
  2. Login as USER-A in parent portal: (user should be able to see the pega case ids in parent portal assigned to them
  3. User should open the case link (to work on it), then through IAC, pega application is called, case is opened in perform mode in the same window
  4. User will work on the case
  5. Log off from parent portal
  6. Login as User-B in parent portal: (user should be able to see their cases in parent portal)
  7. User clicks on a case link, through IAC , pega application is called,
  8. Observe Case does not open

Root Cause



When the user was logging off from the parent portal they were not logging off from PRPC.  Subsiquent calls to PRPC were simply using the same requestor. The portal logoff action did not include any handling for logging off PRPC. 

Resolution



To solve this problem we added the following to the gadget HTML used to display the PRPC content:

<script>
window.onunload = logoffPRPC;

function logoffPRPC() {

        var logoffURL =         pega.web.config.gatewayURL+pega.web.config.systemID+"/!"+pega.web.config.appName+"/$"+pega.web.config.thread+"?pyActivity=%40baseclass.doUIAction&action=logoff";
        xmlhttp=new XMLHttpRequest();
        xmlhttp.open("GET",logoffURL,false);
        xmlhttp.send();
 
}
</script>

Needed to call the logoff in a AJAX request. 

Suggest Edit

Published June 20, 2016 - Updated December 2, 2021

Did you find this content helpful? Yes No

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

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