Issue Summary

Jira Align > Settings > Use Trend > Login Activity shows a user has multiple login activities recorded

This is reproducible on Data Center: yes

When multiple tabs are open, we can see multiple duplicated logins for a user recorded in the Login Activity page in the UI. Attached is the screenshot that shows multiple logins for a user within a few seconds.

This happens when multiple tabs are open and the user is already authenticated on one tab but we are logging it multiple times in the login activity page depending on the number of tabs open.

Support is able to reproduce in both SSO and non-SSO environments. Please see the below steps.

Steps to Reproduce

With SSO:

1. Login to internal.jiraalign.com using SSO
2. Duplicate this to multiple tabs (click on Jira Align application on the Identity provider to open multiple tabs)
3. Logout from Jira Align and all other tabs, you will be back on the Identify Provider landing page
4. Now log back in by selecting the Jira Align application on the Identify provider page.
5. Do this on the rest of the tabs.
6. Result: Check Login Activity page in the UI. Multiple login activities will be recorded on the Login Activity page.

Non-SSO steps:

1. Open one tab for JA
2. User signs in to JA in that tab
3. Check Administration > Use Trend > Login Acitvity and notice only one login activity shows for the user as expected.
4. Open multiple tabs for JA (you can duplicate the above tab, right-click > duplicate)
5. Now log out on one tab
6. Refresh all other tabs. The user will be logged out on all tabs, this is fine
7. Now log in on one tab and the user is authenticated and logged in on that tab
8. Note: Check the other remaining tabs, user is still not logged in/not authenticated on other tabs. This does not seem expected
9. Log in to all other tabs each tab using credentials and clicking 'Sign in'
10. Now check the Login Activity page and notice that multiple logins are recorded for that user- This is not expected as the user should have been authenticated from the first tab so there should be only one login activity for that user as part of the first tab login.
11. Observed Behavior from the above non-SSO test:
    • Once the user logs in to one tab and is authenticated, the user is still not directly authenticated in other tabs. The user needs to sign in on the other remaining tabs as well. As a result, each extra login from other tabs gets recorded as a duplicate login in the login activity log.

Expected Results

For a login attempt at a time, it should show only one login record for a user regardless of the number of open tabs. User should only have to login once in one tab and that authentication should automatically carry over to other tabs.

Actual Results

Multiple duplicated logins are recorded on the login activity page. Even though user is authenticated in one tab, they are not authenticated in other tabs.

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available