000018225 - How to require users to use SecurID to authenticate on some clients  and ACE/Server passwords on other clients.

Document created by RSA Customer Support Employee on Jun 16, 2016Last modified by RSA Customer Support Employee on Apr 21, 2017
Version 2Show Document
  • View in full screen mode

Article Content

Article Number000018225
Applies ToRSA ACE/Server
RSA SecurID Standard Token
User has a password assigned in the ACE/Server
Different login names for same user
IssueHow to require users to use SecurID to authenticate on some clients, and ACE/Server passwords on other clients.
How to use server as a central place for SecurID and passwords.
ResolutionIf you assign an ACE password to a user combined with a token, they are allowed to use either method on any machine they have access on.

Here is an example of how to allow a user to login with a password on specific machines.

EXAMPLE:

ACCOUNT 1
User: Jean Smith
Default Login: jsmith
Token: TOKEN

ACCOUNT 2
User: Jean Smith
Default Login: jsmithpw
Token: PASSWORD

Create two accounts for the user with different Default Logins, like what is listed above.

Assign the account with the token as you normally would, to clients.

If you have a client called internal that you want the user to login using a password, edit the client and activate the user "jsmithpw" on the client. When activating the user, it should prompt you for the users Login and Shell for that client. For Login use "jsmith".
Legacy Article ID6.0.2605345.2853368

Attachments

    Outcomes