- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
RSA security console unsaasign token from unknown user When a User has been deleted from Active Directory
That is cool, I understand that that is due to the user being removed from AD. The question is how to find out what user was assigned the token? We will need to get the Fob back so we need to know who Unknown was. Is there a report that will show who was originally assigned the Token?
- Tags:
- AM
- Auth Manager
- Authentication Manager
- Community Thread
- Discussion
- Forum Thread
- RSA Authentication Manager
- RSA SecurID
- RSA SecurID Access
- SecurID
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
If the AD user was straight up deleted, when you run a Clean up job, the token will be unassigned from this no longer existing user.
You can run this clean up job manually, and individually check all the no longer existing users found and then click to unassign all the token, or you can schedule these jobs to automatically run every night or every few days or whatever, but with a grace period, because we have heard, very rare, but sometimes the AD Administrators mistakenly delete users ( yeah I know what you are thinking, that could never happen!) so if that has happened, you can wait a few days before unassigning those tokens.
If the AD people did delete a user, and then recreated the same user, the AM Identity source would still find that user even though their ObjectGUID had changed, because all the other information is the same, first and last name, UserID, DN.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
If the AD user was straight up deleted, when you run a Clean up job, the token will be unassigned from this no longer existing user.
You can run this clean up job manually, and individually check all the no longer existing users found and then click to unassign all the token, or you can schedule these jobs to automatically run every night or every few days or whatever, but with a grace period, because we have heard, very rare, but sometimes the AD Administrators mistakenly delete users ( yeah I know what you are thinking, that could never happen!) so if that has happened, you can wait a few days before unassigning those tokens.
If the AD people did delete a user, and then recreated the same user, the AM Identity source would still find that user even though their ObjectGUID had changed, because all the other information is the same, first and last name, UserID, DN.
