Modern Session Timeout Does Not Display Login Page To User
search cancel

Modern Session Timeout Does Not Display Login Page To User

book

Article ID: 370211

calendar_today

Updated On:

Products

Clarity PPM SaaS

Issue/Introduction

When the session timeout is encountered, the user is not provided a login page to start a new session.
Users do not know why various generic error messages appear, depending on what workspace or tile is clicked.

Steps To Reproduce:
1. Login to Clarity with a non-SSO login
2. Set and wait for the timeout, e.g. 1 minute

Expected: It should work the same way as Classic where it gives a login page.
When in the Modern UX, if a user session gets hit with a timeout, it does not prompt the
user with a login page to allow users to log in to resume work.

Actual: Modern pages/frames still display to user.
When user assumes session is still valid, users start clicking workspaces shown only to get generic error messages:

-Undefined
-global.errors.load.couldNotRetrievePreference
-An error occurred while retrieving preferences

HAR file shows:
401 Unknown Reason

This server could not verify that you
are authorized to access the document
requested.  Either you supplied the wrong
credentials (e.g., bad password), or your
browser doesn't understand how to supply
the credentials required

Resolution

Check the proxy server configuration and how it interacts with the Classic vs the Modern UX.

1. For Classic, when a session is timed out and user accesses a link/page, it will not generate a 401 error, but rather, it redirects to a login session.

2. For Modern UX, since it is more intuitive, it generates a 401 error.
This 401 error is being interpreted by the Reverse Proxy and is trying to redirect to a default custom page designed for the 401 Error being sent by the proxy server, rather
than the response from server. 

The following options for the server team are:

1. Do not use the proxy server with Clarity

2. Remove the ErrorDocument configuration for 401 in the proxy configuration as per article:
https://httpd.apache.org/docs/2.4/custom-error.html