Problem Note 58120: When opening a stored process in SAS® Visual Analytics, an "Unauthorized" error might be displayed
In an environment configured for Single Sign On (SSO), SAS Visual Analytics might display Unauthorized 401
error when you attempt to re-open a stored process. This error occurs because the web browser caches the first server response. Because subsequent browser calls for the same stored process use this cached information, you see this error if the cached ticket has expired.
To determine whether you are encountering this problem, clear the browser cache. However, clearing the browser cache is a temporary solution.
The long-term workaround is to modify web.xml
file for SAS Visual Analytics Transport Services. This change adds a one-minute expiration for a 301-redirect response. This delay prevents long-term caching.
- Locate the following file:
<sas-config-dir>/Web/WebAppServer/SASServer12_1/sas_webapps/sas.bitransportservices.war/WEB-INF
/web.xml
- Make a backup of the file, and then open the active copy in a plain text editor.
- Add the following two sections in the appropriate places, maintaining
web.xml
restrictions for the order of sections and elements.
<filter>
<filter-name>ExpiresFilter</filter-name>
<filter-class>org.apache.catalina.filters.ExpiresFilter</filter-class>
<init-param>
<param-name>ExpiresDefault</param-name>
<param-value>access plus 1 minute</param-value>
</init-param>
<init-param>
<param-name>ExpiresExcludedResponseStatusCodes</param-name>
<param-value>200, 302, 401, 404, 500, 503</param-value>
</init-param>
</filter>
<filter-mapping>
<filter-name>ExpiresFilter</filter-name>
<url-pattern>/onebi/services/ssoRedirect</url-pattern>
<dispatcher>REQUEST</dispatcher>
</filter-mapping>
- Restart the web application server where SAS Visual Analytics is deployed.
Note: If you rebuild and redeploy SAS Visual Analytics, the web.xml
file is overwritten. You must redo the workaround steps.
Operating System and Release Information
SAS System | SAS Visual Analytics | Microsoft® Windows® for x64 | 7.3 | | 9.4 TS1M3 | |
Linux for x64 | 7.3 | | 9.4 TS1M3 | |
*
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.
In an environment configured with Single Sign On (SSO), some requests are cached on browser (client) side. As a result, subsequent calls to a stored process might use old or expired tickets from the SAS Logon Manager. As a workaround, you can modify the web.xml file for transport services.
Type: | Problem Note |
Priority: | high |
Date Modified: | 2016-06-28 09:25:17 |
Date Created: | 2016-04-27 09:38:14 |