Summary

An unresponsive browser and page hanging issue was experienced while navigating Jira Align actively along with using multiple tabs and clicking the Jira Align issue link from the Jira instance at the same time.

Environment

Jira Align Cloud

Diagnosis

If a user clicks on the same link from Jira multiple times within a short time interval and tries to perform an action on another logged-in Jira Align page while the other page is still loading, due to the SSO security validation check the session is terminated while validating the web tokens to prevent multiple concurrent logins.

The initial exception is raised by the SQL stating that there are multiple key session state objects, and not possible to proceed with the active session. This is the reason that the IdP attempts when the user clicks the Feature while the same Feature (session) is still populating on another browser tab.

"Violation of PRIMARY KEY constraint 'SessionState'. Cannot insert duplicate key in object 'SessionState"

• Then the "Web Login Token Validation" action takes place where the error is raised "Both web login tokens do not match". This is to validate web tokens to prevent multiple concurrent logins and provide the ability to log out a user using the token.

Level: Warning
   MessageTemplate: Both web login tokens do not match
   Properties: { [-]
     Action: WebLoginTokenValidation
     Event: AuthenticationModule.Module_PostAuthenticateRequest

• And a post back validation happens, if the post is not valid from anti-forgery token validation, showing an error page message. Also, the "Whoops" error is visible on the page. And the page is frozen till the user re-login. Re-login fixed the issue since the token is refreshed.

XX/XX/2023
16:55:24.398	
{ [-]
   ASP_function: OOFunctionsXSRF.ValidatePostback
   ValidatePostback: False
   correlationid: XXXXXXEePj/cA/XXXX=
   customer_db: XXX
   error_description:
   error_number: 0
   error_source:
 

Cause

Due to the SSO security validation check the session is terminated while validating the web tokens to prevent multiple concurrent logins. Thus, this is working as designed and the behavior is expected as per the code as well.

Solution

This is a race condition and the suggestion here is to avoid opening multiple links from Jira while one of them is still populating and the user has already an active session in the Jira Align.