SAS Token Authentication - launch credential must be group account?

[Madelyn_SAS]

Note that SAS does not recommend modifying the membership of the SAS General Servers group.

http://support.sas.com/documentation/cdl/en/bisecag/69827/HTML/default/viewer.htm#n07km0roa3fnpfn1oi...

Also, SAS Trust is a highly privileged user and SAS does not recommend modifying this user either

http://support.sas.com/documentation/cdl/en/bisecag/69827/HTML/default/viewer.htm#n1wyid30nrcynhn1q1...

You should be able to select an account to use for token authentication by choosing an account that meets the criteria for a launch credential.

http://support.sas.com/documentation/cdl/en/bisecag/69827/HTML/default/viewer.htm#p18wh3fg2jlhegn0zm...

Most customers would use the Login for the SAS General Servers group (SASSRV, by default) as the account to use for token authentication for the standard workspace server. This account is already used by the Stored Process Server and the Pooled Workspace Server, so it meets the criteria.

Is there a reason why you do not want to use the SASSRV account?

[Teja]

Hi,

Thank you all for your help. Issue is resolved. I am using SASSRV account to launch the work space server.

But i noticed that all the Sessions and files in work directory are now owned with SASSRV account. is there a way which directories in SASWork are associated to which SAS Session. We have SAS Grid and all the jobs are have SASSRV user as owner. I cannot find which job is related to the SASWORK director in case if any one consuming more space in SASWORK location i cannot kill the corresponding JOB.Any thoughts on this.

Thank you very much for all your responses.

Thanks,

Ravi. 

[Kurt_Bremser]

The process number of the process owning a WORK directory is coded into the directory name, in hexadecimal notation. Use a converter like https://www.easycalculation.com/hex-converter.php to show the decimal values of the portions of the directory name.

[ravi15]

Hi 

This is the directory name i see in the saswork

SAS_workBDE70000148D_usflsas1.wst.corproot.com

BDE70000148D if this is the HEX value when i convert it to decimal 208799835100301. this is too big for the JOBID.

Anything i am missing here. 

[Kurt_Bremser]

It's either the first or second half of the hex-coded part. Just play around a little with the values till you get a valid existing process number.

(I have no access to the SAS server at the moment)

[nhvdwalt]

Just use 148D which translates to a PID of 5261 on server usflsas1.wst.corproot.com