sasadm@saspw password recovery

[japsas100]

@SASKiwi 

I can't see the IWA option in SAS 9.2 SMC.

[SASKiwi]

@japsas100  - Could be because you are running with a SAS linux server or it didn't become available until a later SAS release.

[AnandVyas]

Hi @japsas100 

Usually when you launch SMC and create a profile to make a connection to metadata a SAS profile file is created under /home/sas/.SASAppData/MetadataServerProfiles with the name you have given during profile creation ( example: SASAdmin.swa).

If your site has the metadata option save local password set to yes this file also stores the encrypted password of the sasadm account. If it's there you won't be asked to enter password during the next launch of SMC. I think you can use this file to launch SMC using encoded password. I haven't tried it but you can give it a shot!

[japsas100]

Thanks @AnandVyas 

I have added the sasadm@saspw encrypted password to the /home/sas/.SASAppData/MetadataServerProfiles and its working fine. Thanks for the suggestion.

Is there any way to launch SAS Deployment manager by adding the encrypted password same as I did for sas management console.

Another question:

if we already know the current sasadm@saspw password? Do we need to stop/start any services after changing the password with smc/sdm?

[AnandVyas]

Hi @japsas100 

Every time you launch SAS Deployment Manager or SAS Deployment Wizard, different options you provide as part of the wizard are stored into a response file and then used to run action/task you have selected. While providing values for these options, few steps are also verified in the background.

For example when you perform a change and enter password to metadata server, connection to metadata is verified.

Now that you don't know what the real password is you can actually run the wizard in record mode to generate a properties file and use that file to perform the task you wish to. Now the catch is in record mode even though the task isn't actually performed you will still be asked to enter the password and it will be validated so either you will have to get a sample file from your non-prod environment or seek for assistance from support.

For the second Q: After changing any value in the configuration file which is read during service startup you will always have to restart services. Mostly during internal passwords, sassrv etc.