If you are inactive for a period of time (30 minutes by default), SAS Event Stream Processing Studio or SAS Event Stream Manager signs you out automatically. When this automatic sign-out occurs, you are prompted to sign in to the respective application again.
When you successfully enter your credentials and log in again after this time-out, you are redirected to a page telling you to sign out. The pop-up message on this page reads similar to the following:

(You have signed in. For increased security, sign out and close your web browser when you finish accessing services that require authentication.)
Note: This issue occurs only when you attempt to sign in again after being automatically logged out due to inactivity. It does not occur during initial sign in.
If you have not set a configuration option for the SAS Logon Manager, you might not be properly redirected to the main application page when you run the following applications:
- SAS® Event Stream Manager 5.1
- SAS® Event Stream Manager 5.2
- SAS® Event Stream Processing Studio 5.1 (in Viya integration mode)
- SAS® Event Stream Processing Studio 5.2
Workarounds
There are two workarounds for this issue.
Workaround 1
Manually navigate to the correct URL for the application homepage.
For example, for SAS Event Stream Processing Studio, navigate to the following:
http://localhost:80/SASEventStreamProcessingStudio/index.html
Workaround 2
The SAS Logon Manager sas.logon.callback configuration option is not set up to handle this redirect by default. To fix the redirect, set the value for the sas.logon.callback configuration option to /**.
You can set this option using one of the following methods:
A. Using SAS® Environment Manager (if installed):
Complete the following steps in the SAS Environment Manager to circumvent the issue:
- Navigate to the SAS Environment Manager login page.
- Log in to SAS Environment Manager (Note: The user needs admin privileges).
- Select Configuration from the left pane.
- In the drop-down menu, change the view to Definitions.
- Enter sas.logon.callback in the search filter.
- Select sas.logon.callback.
- Click New Configuration.
- Enter /** in the allowed.uris field.
- Click Save.
B. Using the command-line interface (CLI):
You can use /opt/sas/viya/home/bin/sas-bootstrap-config to write a key/value directly to Consul to circumvent the issue.
Key: /config/SASLogon/sas/logon/callback/allowed/uris
Value: /**
Here is an example:
sudo /opt/sas/viya/home/bin/sas-bootstrap-config --consul https://localhost:8501 --token-file /opt/sas/viya/config/etc/SASSecurityCertificteFramework/tokens/consul/default/client.token kv write --force config/SASLogon/sas.logon.callback/allowed.uris /**
Note: The sudo command is necessary only if you are not running as the sas or root user.
For more information about using sas-bootstrap-config, see SAS Bootstrap Config CLI Commands in SAS® Viya® 3.4 Administration: Orientation
After you have changed this option for SAS Logon Manager, you should then be directed to the application home page upon successful log in.
Operating System and Release Information
| SAS System | SAS Event Stream Processing Engine | Microsoft® Windows® for x64 | 5.1 | | | |
| Linux for x64 | 5.1 | | | |
| SAS System | SAS Event Stream Manager | Linux for x64 | 5.1 | | Viya | |
*
For software releases that are not yet generally available, the Fixed
Release is the software release in which the problem is planned to be
fixed.