Problem Note 69256: The SAS® Risk Governance Framework fails to authenticate to the Logical Workspace Server when you run a cycle in SAS® Risk Stratum
By default, the SAS Risk Governance Framework runs SAS code on the Logical Pooled Workspace Server when you run a cycle in SAS Risk Stratum. If you configure the web application to run the code on the Logical Workspace Server instead, the web application might fail to authenticate to the workspace server. When the problem occurs, the catalina.out log contains an error similar to the following:
com.sas.svcs.authentication.client.MissingIdentityForDomainException: The user "RGF Administrator" could not log on to the server "SASApp - Logical Workspace Server". The application could not log on to the server "host-name:port". The user ID "user-ID" or the password is incorrect. No host credentials exist to start server SASApp - Workspace Server (A53E0IMS.AY00000D). Either the client needs to send in host credentials, or credentials need to be specified for the server. Insufficient information provided for a connection to the metadata server.
Click the Hot Fix tab in this note to access the hot fix for this issue.
After installing the hot fix, you can specify the following new property in the configdata.properties file to enable authentication when you configure the web application to use the Logical Workspace Server:
monitor.background.auth.mode = clone
Operating System and Release Information
SAS System | SAS Risk Governance Framework | Microsoft Windows Server 2012 R2 Datacenter | 7.4 | 7.5 | 9.4 TS1M5 | 9.4 TS1M8 |
Microsoft Windows Server 2012 Datacenter | 7.4 | 7.5 | 9.4 TS1M5 | 9.4 TS1M8 |
Microsoft Windows 8 Pro x64 | 7.4 | 7.5 | 9.4 TS1M5 | 9.4 TS1M8 |
Microsoft Windows Server 2008 for x64 | 7.4 | 7.5 | 9.4 TS1M5 | 9.4 TS1M8 |
Microsoft Windows Server 2008 R2 | 7.4 | 7.5 | 9.4 TS1M5 | 9.4 TS1M8 |
Microsoft Windows Server 2008 | 7.4 | 7.5 | 9.4 TS1M5 | 9.4 TS1M8 |
Microsoft Windows 10 | 7.4 | 7.5 | 9.4 TS1M5 | 9.4 TS1M8 |
Microsoft Windows 8.1 Pro x64 | 7.4 | 7.5 | 9.4 TS1M5 | 9.4 TS1M8 |
Microsoft Windows 8.1 Pro 32-bit | 7.4 | 7.5 | 9.4 TS1M5 | 9.4 TS1M8 |
Microsoft Windows 8.1 Enterprise x64 | 7.4 | 7.5 | 9.4 TS1M5 | 9.4 TS1M8 |
Microsoft Windows 8 Pro 32-bit | 7.4 | 7.5 | 9.4 TS1M5 | 9.4 TS1M8 |
Microsoft® Windows® for x64 | 7.4 | 7.5 | 9.4 TS1M5 | 9.4 TS1M8 |
Microsoft Windows 8 Enterprise 32-bit | 7.4 | 7.5 | 9.4 TS1M5 | 9.4 TS1M8 |
Microsoft Windows 8.1 Enterprise 32-bit | 7.4 | 7.5 | 9.4 TS1M5 | 9.4 TS1M8 |
Microsoft Windows 8 Enterprise x64 | 7.4 | 7.5 | 9.4 TS1M5 | 9.4 TS1M8 |
Microsoft Windows Server 2012 R2 Std | 7.4 | 7.5 | 9.4 TS1M5 | 9.4 TS1M8 |
Microsoft Windows Server 2012 Std | 7.4 | 7.5 | 9.4 TS1M5 | 9.4 TS1M8 |
Microsoft Windows Server 2016 | 7.4 | 7.5 | 9.4 TS1M5 | 9.4 TS1M8 |
Windows 7 Enterprise 32 bit | 7.4 | 7.5 | 9.4 TS1M5 | 9.4 TS1M8 |
Windows 7 Enterprise x64 | 7.4 | 7.5 | 9.4 TS1M5 | 9.4 TS1M8 |
Windows 7 Home Premium 32 bit | 7.4 | 7.5 | 9.4 TS1M5 | 9.4 TS1M8 |
Windows 7 Home Premium x64 | 7.4 | 7.5 | 9.4 TS1M5 | 9.4 TS1M8 |
Windows 7 Professional 32 bit | 7.4 | 7.5 | 9.4 TS1M5 | 9.4 TS1M8 |
Windows 7 Professional x64 | 7.4 | 7.5 | 9.4 TS1M5 | 9.4 TS1M8 |
Windows 7 Ultimate 32 bit | 7.4 | 7.5 | 9.4 TS1M5 | 9.4 TS1M8 |
Windows 7 Ultimate x64 | 7.4 | 7.5 | 9.4 TS1M5 | 9.4 TS1M8 |
Linux for x64 | 7.4 | 7.5 | 9.4 TS1M5 | 9.4 TS1M8 |
*
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.
Type: | Problem Note |
Priority: | high |
Date Modified: | 2023-02-16 10:37:51 |
Date Created: | 2022-06-02 16:54:54 |