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
Reports Number of Views Operating System Access Number of Views Product Updates Number of Views Allow a User to Authenticate Without an RSA SecurID PIN Number of Views Edit Session Lifetime Settings for Operating System Access Number of Views
Trending Articles
Passwordless Authentication in Windows MFA Agent for Active Directory – Quick Setup Guide RSA Authentication Manager 8.9 Release Notes (January 2026) RSA Authentication Manager Upgrade Process RSA Authentication Manager 8.7 SP2 Setup and Configuration Guide An example of SSO using SAML and ADFS with RSA Identity Management and Governance 6.9.x
Don't see what you're looking for?
