How to require users to use SecurID to authenticate on some clients and ACE/Server passwords on other clients.
Originally Published: 2000-09-19
Article Number
Applies To
RSA SecurID Standard Token
User has a password assigned in the ACE/Server
Different login names for same user
Issue
How to use server as a central place for SecurID and passwords.
Resolution
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".
Related Articles
Error message "Our process does not support use of public accounts" when registering for an RSA Community or myRSA account Number of Views RSA Announces RSA Authentication Manager 8.7 SP1 Patch 3 and Updated Web-Tier Server Number of Views RSA Announces RSA Authentication Manager 8.8 Patch 2 and Updated Web-Tier Server Number of Views How to obtain the version information for RSA Authentication Agent for PAM installed on Linux Number of Views RSA Announces RSA Authentication Manager 8.8 Patch 1 and Updated Web-Tier Server Number of Views
Trending Articles
RSA Authentication Manager Upgrade Process How to Update the Root (Server) and Client Certificates in RSA Identity Governance & Lifecycle RSA Authenticator 6.2.2 for Windows Administrator Guide RSA SecurID software token .sdtid file fails to import into RSA SecurID Software Token 5.0 for Windows RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide
Don't see what you're looking for?
