Announcements

SecurID® Discussions

Browse the SecurID discussion board to get product help and collaborate with other SecurID users.
TJReed
Beginner
Beginner

Users never logged in with token

Jump to solution

All,

  Running the Users never logged in with token report I get an unexpected result.  We know there are users who never used their RSA Token to access our network.  The report supports this by not showing any entries in the column “Last Used to Authenticate”.  However, the report also shows a few users with entries in the “User Last Authentication Date”.  How can this happen?  If a user has not used their token to log in, there should not be any entries in either column.  The ONLY exception I can think of is:  If the userid is used to access the RSA Security Console or Operations console.  (tradmin is a userid which has access to the RSA Security and Operations Console; smccrea does not have this access).

0 Likes
1 Solution

Accepted Solutions
EdwardDavis
Employee
Employee

make sure you are on the latest patch 8.1 sp1 patch 13, as some reports have issues and have been remedied in patches

View solution in original post

7 Replies
EdwardDavis
Employee
Employee

make sure you are on the latest patch 8.1 sp1 patch 13, as some reports have issues and have been remedied in patches

_EricaChalfin
Employee (Retired) Employee (Retired)
Employee (Retired)

Click the link to download Authentication Manager 8.1 SP1 patch 13.

0 Likes

Edward,

Thank you.

 

I just read the README for AM v8.1 SP1 patch 13.  I did not notice a fix for my issue.  Is it normal for RSA to not list all the fixes in their Patches?

 

T.J.

0 Likes
BrianTwomey
Employee
Employee

Hi T.J.

 

The readme doesn't always contain a listing of every single fix in a given patch. One other thing to mention in regards to your question regarding users that have never logged in with a token. If you had migrated from a previous version of Authentication Manager then it may show a date of 1986 which was a default date shown when a user had never authenticated. This would carry over during a migration. Other than that if the user had logged into one of the RSA consoles could update that field.

0 Likes

Thank you.

Ok.  I will upgrade.

 

One last question, when I upgrade a Patch, does the Authentication Manager require a reboot?

 

T.J.

0 Likes
BrianTwomey
Employee
Employee

It doesn't require a reboot but it does restart services.

0 Likes
StevenSpicer
Valued Contributor Valued Contributor
Valued Contributor

You are close. A user may have more than one authenticator: multiple tokens, or On Demand Authentication, or Risk Based Authentication, or a password to the Consoles. The "Last Used to Authenticate" column shows the timestamp for the usage of a specific token, and might be empty, but the the "User Last Authentication Date" shows the last time the user authenticated with ANY authenticator, not just that token.

0 Likes