https://communities.sas.com/t5/Administration-and-Deployment/SAS-Auuthentication-after-RHEL-7-7-Upgrade/m-p/618278#M18031 <P>Thank you for looking at my post. I found the issue. The messages file for the OS provided a clue that there was an issue with authentication from Metadata. I discovered that the setuid script needed to be run in SASFoundation in the metadata tier. Once this was run everything started working.</P> Sat, 18 Jan 2020 18:47:23 GMT DJWanna 2020-01-18T18:47:23Z https://communities.sas.com/t5/Administration-and-Deployment/SAS-Auuthentication-after-RHEL-7-7-Upgrade/m-p/618267#M18030 <P>Urgent assistance needed, sorry. Last night I applied some hotfixes, our Linux team also upgraded the OS from RHEL 7.6 to RHEL 7.7. Now no one can use SAS. It appears to be something with authentication. I am able to execute sas from the command line, SASGSUB is able to touch a file. A KRB ticket is getting created yet in Enterprise Guide the user name/password window keeps returning. In web applications the error is user name/password invalid. The hotfixes that were applied are:</P> <P>&nbsp;</P> <P>Base SAS (B6Q090, 64-bit, English Update):<BR />SAS High-Performance Risk Server Component (D1W003, 64-bit, English Update):<BR />SAS Risk and Finance Workbench Server (D4M005, 64-bit, English Update):<BR />SAS Scalable Performance Data Client (C8Z003, 64-bit, English Update):<BR />SAS Threaded Kernel (C1S010, 64-bit, English Update):<BR />SAS/ACCESS Interface to ODBC (B7V002, 64-bit, English Update):<BR /><BR /></P> <P>I have checked to make sure the setuid was applied. The only difference I can really see is that there are two processes that are no longer running:</P> <P>root@svcksa69901a3u # ps -aef | grep krb</P> <P>vaultsas 194270 194080&nbsp; 0 Jan04 ?&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 00:00:08 /sas/sys/platform_prod/pm/10.1/linux2.6-glibc2.3-x86_64/etc/krbrenewd</P> <P>vaultsas 196578 195877&nbsp; 0 Jan04 ?&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 00:00:29 /sas/sys/platform_prod/lsf/10.1/linux2.6-glibc2.3-x86_64/etc/krbrenewd</P> <P>&nbsp;</P> <P>Could lack of these running be causing this authentication issue? How does this autostart?</P> <P>&nbsp;</P> <P>Thank you for your guidance.</P> Sat, 18 Jan 2020 16:20:17 GMT https://communities.sas.com/t5/Administration-and-Deployment/SAS-Auuthentication-after-RHEL-7-7-Upgrade/m-p/618267#M18030 DJWanna 2020-01-18T16:20:17Z https://communities.sas.com/t5/Administration-and-Deployment/SAS-Auuthentication-after-RHEL-7-7-Upgrade/m-p/618278#M18031 <P>Thank you for looking at my post. I found the issue. The messages file for the OS provided a clue that there was an issue with authentication from Metadata. I discovered that the setuid script needed to be run in SASFoundation in the metadata tier. Once this was run everything started working.</P> Sat, 18 Jan 2020 18:47:23 GMT https://communities.sas.com/t5/Administration-and-Deployment/SAS-Auuthentication-after-RHEL-7-7-Upgrade/m-p/618278#M18031 DJWanna 2020-01-18T18:47:23Z