SAS® Risk Stratum cycle creation fails due to a concurrent session policy with "an unexpected server error occurred"


In some scenarios, cycle creation might fail with the following error message:

An unexpected server error occurred


In addition, errors similar to the following might occur the SAS Risk Governance Framework (RGF) middle-tier logs located in <SAS-Configuration Directory>/LevX/Web/Logs/SASServer8_1/SASRiskGovernanceFrameworkMidTier.log (where X is the Level in your environment):

SASRiskGovernanceFramework XXXXX XX:XX:XX [tomcat-http--44] DEBUG com.sas.commons.rest.cas.TicketingRestTemplate  - Reading [java.lang.String] as "text/html;charset=UTF-8" using [org.springframework.http.converter.StringHttpMessageConverter@1d3d19d7]
SASRiskGovernanceFramework XXXXX XX:XX:XX [tomcat-http--44] ERROR com.sas.oprisk.monitor.rest.controller.UIContextController  - Exception initializing UI context
org.json.JSONException: A JSONObject text must begin with '{' at  character XX of 

This issue typically occurs when you configure a Concurrent Session Policy with either the *Deny or **Logoff option. When this policy is enforced, it might interfere with user interface (UI) context initialization during cycle creation, which results in the error.

Workaround

To work around this issue, you must remove or disable the Concurrent Session Policy in the SAS Application Infrastructure by completing the following steps:

  1. Log on to SAS® Management Console.
  2. Go to the Plug-ins tab.
  3. Navigate to Application Management ► Configuration Manager.
  4. Right-click SAS Application Infrastructure and select Properties.
  5. In the Properties window, click the Advanced tab.
  6. Locate and delete the following policy, if present: Policy.ConcurrentUserLogins.                                  
    7. Click OK to save the changes.
    8. Restart SAS® Web Application Server for the changes to take effect.

Application Management ► Configuration Manager ► right-click SAS Application Infrastructure ► Properties ► the Advanced tab ► locate and delete Policy.ConcurrentUserLogins.

*deny

When you specify deny, users receive a message from SAS Logon Manager that a session is already active. The user cannot sign on until the existing session expires or an administrator uses the SAS Web Administration Console to Force Sign Out the user.

**logoff 

When you specify logoff, the existing session is logged off, and the user is logged on to the requested web application.