BookmarkSubscribeRSS Feed
☑ This topic is solved. Need further help from the community? Please sign in and ask a new question.
Fluorite | Level 6

Hi @gwootton ,


Thank you for all the help!


While attempting to access SAS Studio, I encountered the following error:

"A connection to the SAS Compute Server was unavailable."




I have checked the logs of the relevant components. see below:

A session has been requested for the context with the ID "9c1c50f9-33e1-43a2-b615-7ebad9c0d0b1".

caused by: org.springframework.web.client.HttpClientErrorException$NotFound: 404 : "{"errorCode":10580,"message":"The identifier values for USER \"sasboot\" were not found.","details":["traceId: 9e62dc6d6980982c","path: /identities/users/@currentUser/identifier"],"links":[],"version":2,"httpStatusCode":404}"

The compute session could not be created.


The documentation specifies that the SAS Viya platform supports only LDAP, Kerberos, and single sign-on methods for authenticating users who are signing in to the environment. Is it not possible to establish user accounts with passwords instead?

Could you please suggest on this?


This error is because sasboot is a special account for Viya configuration, it cannot be used with SAS Studio.
You would need to log in to Viya with a normal user account.
You cannot add users to Viya directly, only through identity provisioning using LDAP or SCIM. You can authenticate to Viya using LDAP (providing a user ID and password), Kerberos, or SSO like OIDC and SAML.
Greg Wootton | Principal Systems Technical Support Engineer

suga badge.PNGThe SAS Users Group for Administrators (SUGA) is open to all SAS administrators and architects who install, update, manage or maintain a SAS deployment. 

Join SUGA 

Get Started with SAS Information Catalog in SAS Viya

SAS technical trainer Erin Winters shows you how to explore assets, create new data discovery agents, schedule data discovery agents, and much more.

Find more tutorials on the SAS Users YouTube channel.

Discussion stats
  • 16 replies
  • 2 in conversation