<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: SAS Viya 3.5 CAS Host Account in Administration and Deployment</title>
    <link>https://communities.sas.com/t5/Administration-and-Deployment/SAS-Viya-3-5-CAS-Host-Account/m-p/774869#M23247</link>
    <description>&lt;P&gt;Ended up figuring it out with SAS TS.&amp;nbsp; Apparently the SSSD service on one of the nodes wasn't refreshing and any new users added to the Active Directory group wasn't being recognized on this node.&amp;nbsp; In working with our Linux admin, once SSSD was stopped, cache cleared and restarted, it resolved the issue.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;For reference, this was what was run to refresh the SSSD service...&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P class="lia-indent-padding-left-30px"&gt;service sssd stop ; rm -f /var/lib/sss/db/* /var/log/sssd/* ; service sssd start&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks,&lt;/P&gt;
&lt;P&gt;John&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Mon, 18 Oct 2021 12:33:37 GMT</pubDate>
    <dc:creator>jwward65</dc:creator>
    <dc:date>2021-10-18T12:33:37Z</dc:date>
    <item>
      <title>SAS Viya 3.5 CAS Host Account</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/SAS-Viya-3-5-CAS-Host-Account/m-p/774222#M23231</link>
      <description>&lt;P&gt;I have found lots of information regarding the CASHostAccountRequired group and everything I found says to use this functionality, the user needs to have a CAS Host Account, but yet I cannot find any information or documentation on how to actually accomplish this.&amp;nbsp; Does anyone have any guidance on this?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Scenario:&lt;/P&gt;
&lt;P&gt;We have ALL users in Active Directory groups that are in the custom CASHostAccountRequired group, but yet only some users are not able to start a CAS session!&amp;nbsp; I can't figure out why this doesn't effect ALL users.&amp;nbsp;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="jwward65_2-1634219598357.png" style="width: 400px;"&gt;&lt;img src="https://communities.sas.com/t5/image/serverpage/image-id/64702i782BAC6282077116/image-size/medium?v=v2&amp;amp;px=400" role="button" title="jwward65_2-1634219598357.png" alt="jwward65_2-1634219598357.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="jwward65_0-1634219387107.png" style="width: 400px;"&gt;&lt;img src="https://communities.sas.com/t5/image/serverpage/image-id/64700iF43298D691AC48E2/image-size/medium?v=v2&amp;amp;px=400" role="button" title="jwward65_0-1634219387107.png" alt="jwward65_0-1634219387107.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 14 Oct 2021 13:53:59 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/SAS-Viya-3-5-CAS-Host-Account/m-p/774222#M23231</guid>
      <dc:creator>jwward65</dc:creator>
      <dc:date>2021-10-14T13:53:59Z</dc:date>
    </item>
    <item>
      <title>Re: SAS Viya 3.5 CAS Host Account</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/SAS-Viya-3-5-CAS-Host-Account/m-p/774344#M23233</link>
      <description>If a user is a member of the custom group CASHostAccountRequired, it instructs their CAS session to start as that user rather than the user "cas". So by a CAS host account we mean that the user must exist on the CAS server hosts. I'm guessing that the users who cannot start CAS sessions are not able to own processes on the CAS server hosts. Sounds like however you are provisioning accounts on the servers, like PAM/SSSD, is pulling a different set of identities than Viya.</description>
      <pubDate>Thu, 14 Oct 2021 20:05:07 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/SAS-Viya-3-5-CAS-Host-Account/m-p/774344#M23233</guid>
      <dc:creator>gwootton</dc:creator>
      <dc:date>2021-10-14T20:05:07Z</dc:date>
    </item>
    <item>
      <title>Re: SAS Viya 3.5 CAS Host Account</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/SAS-Viya-3-5-CAS-Host-Account/m-p/774869#M23247</link>
      <description>&lt;P&gt;Ended up figuring it out with SAS TS.&amp;nbsp; Apparently the SSSD service on one of the nodes wasn't refreshing and any new users added to the Active Directory group wasn't being recognized on this node.&amp;nbsp; In working with our Linux admin, once SSSD was stopped, cache cleared and restarted, it resolved the issue.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;For reference, this was what was run to refresh the SSSD service...&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P class="lia-indent-padding-left-30px"&gt;service sssd stop ; rm -f /var/lib/sss/db/* /var/log/sssd/* ; service sssd start&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks,&lt;/P&gt;
&lt;P&gt;John&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 18 Oct 2021 12:33:37 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/SAS-Viya-3-5-CAS-Host-Account/m-p/774869#M23247</guid>
      <dc:creator>jwward65</dc:creator>
      <dc:date>2021-10-18T12:33:37Z</dc:date>
    </item>
  </channel>
</rss>

