SAS Viya web applications might exhibit slow performance in a clustered environment that is running the Identities service on more than one machine. The following actions are examples where you might see long wait times:

• logging in using the SASLogon sign-in page
• switching from viewing Users to viewing Groups within the Users page in SAS^® Environment Manager
• viewing authorizations on an item
• loading content in SAS^® Drive

You might also notice an unusually high number of requests to LDAP from SAS Viya.

This behavior can occur if the Identities service cache becomes locked. When the cache is locked, every request to the Identities service causes a query to use LDAP rather than to cache, thereby bypassing the performance gain that cache provides.

Messages similar to the following in the Identities service log indicate that a request was sent to LDAP:

Note: Trace-level logging on the Identities service for the logger com.sas.identities is required to see the above log data. Refer to the Specify the Threshold Level for Service Logs section in SAS^® Viya^® 3.4 Administration / Logging for the steps to enable this logging level if you want to confirm these messages in your environment. Be aware that some queries to LDAP are normal and required, even if there is no problem accessing the cache.

When the cache is being used, the log shows messages similar to the following instead:

To confirm whether the identities cache is locked, submit these three commands. Each of the three commands should be submitted as a single line, should be run as the SAS user (or a user with sudo privileges), and should be run on the machine that is running the SAS^® Configuration Server:

If the following key (with no value assigned) is in the result, the identities cache is currently locked:

To manually release the cache lock, submit the following command, and then restart the Identities service on each node on which it is running:

Click the Hot Fix tab in this note for a link to instructions about accessing and applying the software update.

Verify that the Update Is Installed

To complete this process, make sure that the Identities service version is 2.17.16 or newer.

You can determine the version of the Identities service using one of these methods:

• On Linux systems, run the following rpm command from the SAS Viya microservices host machine:
  
     rpm -q sas-identities
  
  The version number is shown after the service name. Here is an example:
  
     sas-identities-2.17.16-20200122.1579726744291.x86_64
     
• On Linux or Windows systems, connect to the /identities/apiMeta endpoint. The XML output shows the version similar to the following:
  
     "buildVersion":"2.17.16"
     

Operating System and Release Information

Viya on Windows: An update for this issue is available for SAS Viya 3.4. For instructions on how to access and apply software updates, see the Updating Your SAS Viya software section in the SAS Viya 3.4 for Windows Deployment Guide at

Viya on Linux: An update for this issue is available for SAS Viya 3.4. For instructions on how to access and apply software updates, see the Updating Your SAS Viya software section in the SAS Viya 3.4 for Linux Deployment Guide at