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

Hello
I have a question about the implication of setting  values for   sas.logon.initial.password and  config/identities/sas.identities/administrator in sitedefault.yaml during the installation of SAS Viya4 on openshift using manual deployment.
My question is  : if the values of these two properties are defined in the stitedefault.yaml, can these username and password be used for the initial logon to SAS Environment manager instead of using the sasboot account.?
I would appreciate if anybody can help.

Thanks.

 

1 ACCEPTED SOLUTION

Accepted Solutions
gwootton
SAS Super FREQ
Setting sas.logon.initial.password sets the password for the initial user account, so you don't need to go through the process of setting it using the reset URL in the SAS Logon Manager log.
Setting sas.logon.initial.user sets the username for the initial user account (this is "sasboot" by default).

So these settings are modifying the user ID and password for the initial "sasboot" user, you wouldn't be logging in as this user instead of sasboot, you would be changing the sasboot user ID to something else. It would still be a single, internal account.

Setting sas.identities.administrator lets you define a member of the SAS Administrators group in sitedefault.yaml. This is not necessary for the initial user. In my environments I set this to my personal user ID as well as passing in the LDAP configuration, so I never need to log in as sasboot.


--
Greg Wootton | Principal Systems Technical Support Engineer

View solution in original post

2 REPLIES 2
gwootton
SAS Super FREQ
Setting sas.logon.initial.password sets the password for the initial user account, so you don't need to go through the process of setting it using the reset URL in the SAS Logon Manager log.
Setting sas.logon.initial.user sets the username for the initial user account (this is "sasboot" by default).

So these settings are modifying the user ID and password for the initial "sasboot" user, you wouldn't be logging in as this user instead of sasboot, you would be changing the sasboot user ID to something else. It would still be a single, internal account.

Setting sas.identities.administrator lets you define a member of the SAS Administrators group in sitedefault.yaml. This is not necessary for the initial user. In my environments I set this to my personal user ID as well as passing in the LDAP configuration, so I never need to log in as sasboot.


--
Greg Wootton | Principal Systems Technical Support Engineer
thesasuser
Lapis Lazuli | Level 10

Thanks @gwootton for the prompt response.

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
  • 2 replies
  • 103 views
  • 0 likes
  • 2 in conversation