The SAS/CONNECT UNIX client does not initiate a Kerberos SIGNON to a SAS/CONNECT spawner when the SASCMD SAS global option is set. Instead, when the SAS option SASCMD is set, an MP Connect / SASCMD SAS session is initiated.

A temporary workaround is to clear the value specified for the SASCMD option.

Click the Hot Fix tab in this note for a link to instructions about accessing and applying the software update.

After applying the associated hot fix, you can force the Kerberos SIGNON by specifying USER=_SSPI_ in the SIGNON statement regardless of the value that is specified for SASCMD option.

Operating System and Release Information

Viya on Linux: An update for this issue is available for SAS Viya 3.5. For instructions on how to access and apply software updates, see the Updating Your SAS Viya software section in the SAS Viya 3.5 for Linux Deployment Guide at

A fix for this issue for Base SAS 9.4_M7 is available at: