<?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: Historic Last Login for All Users in Administration and Deployment</title>
    <link>https://communities.sas.com/t5/Administration-and-Deployment/Historic-Last-Login-for-All-Users/m-p/976474#M30332</link>
    <description>The audit functionality is how Viya would surface this information. The sasuser.viya directory is used by the compute server started when using SAS Studio, so would not apply to any user logging into the system.&lt;BR /&gt;If your LDAP server logs bind attempts you might be able to capture the information from there.</description>
    <pubDate>Mon, 06 Oct 2025 15:56:20 GMT</pubDate>
    <dc:creator>gwootton</dc:creator>
    <dc:date>2025-10-06T15:56:20Z</dc:date>
    <item>
      <title>Historic Last Login for All Users</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/Historic-Last-Login-for-All-Users/m-p/976267#M30328</link>
      <description>&lt;P&gt;&lt;STRONG&gt;I had a request to find the last login for all users on my 3.5 Viya environment going back to August 2021.&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Using the Audit CLI plugin, I was able to pull in the last seven days, so that wasn't super useful for this scenario. I then got the last modified timestamp of the &lt;STRONG&gt;~/sasuser.viya&lt;/STRONG&gt; folder for every user. In some cases, that appears to be close enough. But in at least one case, for one of my regular SAS Studio users, they haven't modified that folder going back 3 years, even though they are on the system every day. Some of my users do not even have that folder. I don't know if that means they have never logged in. Or if only certain tools create that folder.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I am curious if anyone has any suggestions or tricks for gathering this info for things that have aged out of the logs at this point. The main use cases in my environment are VA, CAS, and SAS StudioV. We are using LDAP to log in, if that makes a difference, and the login shell is set to &lt;STRONG&gt;/sbin/nologin&lt;/STRONG&gt;; they only access the system via the GUI.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I do have a ticket open with support about this as well.&lt;/P&gt;</description>
      <pubDate>Thu, 02 Oct 2025 19:17:24 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/Historic-Last-Login-for-All-Users/m-p/976267#M30328</guid>
      <dc:creator>five</dc:creator>
      <dc:date>2025-10-02T19:17:24Z</dc:date>
    </item>
    <item>
      <title>Re: Historic Last Login for All Users</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/Historic-Last-Login-for-All-Users/m-p/976474#M30332</link>
      <description>The audit functionality is how Viya would surface this information. The sasuser.viya directory is used by the compute server started when using SAS Studio, so would not apply to any user logging into the system.&lt;BR /&gt;If your LDAP server logs bind attempts you might be able to capture the information from there.</description>
      <pubDate>Mon, 06 Oct 2025 15:56:20 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/Historic-Last-Login-for-All-Users/m-p/976474#M30332</guid>
      <dc:creator>gwootton</dc:creator>
      <dc:date>2025-10-06T15:56:20Z</dc:date>
    </item>
  </channel>
</rss>

