SAS Viya platform web applications can become stuck in a redirect loop in your browser when system clocks are not synchronized on Kubernetes cluster nodes. When this issue occurs, the network trace in the browser developer tools displays HTTP requests that alternate between /SASLogon and other SAS web applications (such as /themes, /appRegistry, and so on). Each request results in an HTTP 302 response code. These requests redirect back to each other continuously, so a seemingly endless loop of these alternating requests occurs.  

When enough of these redirects occur, the browser might display error messages similar to the following:

TOO_MANY_REDIRECTS

or

<hostname> redirected you too many times.

This issue can impact various SAS web applications, such as SAS^® Environment Manager, SAS^® Visual Analytics, SAS^® Studio, and so on. 

This behavior occurs because the “issued at time” value of the authentication token might appear to be from a time in the future if the system clocks are not synchronized on all nodes in the cluster. As a result, the validation of the authentication token can fail, which causes the SAS web to application enter an endless loop that redirects back to /SASLogon. 

Resolution

To resolve this issue, you must ensure that the system clocks are synchronized on all machines in the Kubernetes cluster. Requirements are documented in the SAS^® Viya^® Platform Operations Guide System Requirements section: Kubernetes Cluster Requirements.

Note: Even if the system clocks are off by a seemingly small margin, such as one or two seconds, this issue can still occur.

If you have already confirmed that the system clocks are synchronized, contact SAS Technical Support for assistance with investigating your issue further.