I have a new requirement here. IT migrating users from Domain A to B in AD. I have a test account which is active in new domain B. I have created this new user identity in SMC(B\test) and added to respective SAS users group. We have added SAS_users group and domain users group from the new domain to SAS windows server groups.
Users form new domain were not able to connect to SAS workspace (SASAPP) using IWA from SAS Enterprise Guide. I have verified the object spawner log that new client connection was accepted But if try to expand the SAS application server context it keeps on loading & no errors.
If we use username and password in SAS EG profile It's working fine.
Object spawner running under system and SAS server is trusted for delegation in A domain.
I have verified the local security policy - Log on as a batch job. new domain SAS users group added to nested groups.
It looks like Object spawner not able to pass the credentials. Any suggestions.
Please add these lines to /<SASConfig>/Lev<X>/ObjectSpawner/logconfig.xml:
<logger name="Audit.Authentication"> <level value="Trace"/> </logger>
Restart the object spawner, repeat the problem and send to me the most recent object spawner log for review.
@alexal, I have enabled the workspace server logs but no logs were created. any Idea
The workspace server log should be created because I see that the object spawner has tried to start it:
E:\SAS\config\Lev1\SASApp\WorkspaceServer\WorkspaceServer.bat" -memsize 2147M -realmemsize 2147M /nologo /noterminal /netencryptalgorithm SASProprietary /metaserver server.a.com /metaport 8561 /metarepository Foundation /locale en_US /objectserver /objectserverparms "protocol=bridge spawned
The SAS Users Group for Administrators (SUGA) is open to all SAS administrators and architects who install, update, manage or maintain a SAS deployment.
Learn how to install the SAS Viya CLI and a few commands you may find useful in this video by SAS’ Darrell Barton.
Find more tutorials on the SAS Users YouTube channel.