"Request could not be handled" error when using multiple tabs to access the same RSA Via Lifecycle & Governance application in the same browser
Originally Published: 2016-05-11
Last Modified: 2023-10-06
Article Number
000053117
Applies To
RSA Product Set: RSA Via Lifecycle & Governance (RSA Via L&G)
RSA Product/Service Type: All platforms
RSA Version/Condition: All versions

 
Issue
When the same user is logged into RSA Via L&G from multiple sessions opened in the same browser, movement around the User Interface (UI) may result in a request error: "The request could not be handled," as in the screen shot below:
 
User-added image
Cause
In this situation, there are now two browser panes with the same session ID, and the server cannot distinguish between the separate actions. This can result in the state being corrupted.

 
Resolution
As a best practice, only use the RSA Via L&G application with a single browser session. It is acceptable to be logged in as the same user simultaneously using two different browsers (Google Chrome and Internet Explorer, for example) or on two different computers, as this creates a unique session ID for each session. The problem arises if you clone the existing session, like opening a page in a new tab, or copy a link into another pane.

Engineering ticket ACM-63738 has been opened as an enhancement request for this functionality, however, there are no plans at this time to add this functionality to the product.
Workaround
There are three recommended workarounds.  These are:
  1. Log in to two different browsers;
  2. Log in as two different users; or
  3. Log in using two different URLs, such as https://<hostname>/aveksa/main and https://<ip-address>/aveksa/main.

Related Articles

Trending Articles

Don't see what you're looking for?