Configuring Users for On-Demand Authentication
Users who will receive on-demand tokencodes must be enabled for on-demand authentication (ODA). When a user is enabled, you can specify a delivery method for the tokencodes, the length of time that the user can request on-demand tokencodes, and whether users can set initial PINs using the Self-Service Console. For instructions, see Enable On-Demand Authentication for a User.
An administrator can clear a PIN that is forgotten, expired, or compromised, and then provide a temporary PIN to the user. An administrators can require PIN changes. For more information, see PINs for On-Demand Authentication.
You can configure the Self-Service Console to allow users to update their destination phone numbers and e-mail addresses. This configuration option saves time and effort for the administrators. For instructions, see Enable Users to Update Phone Numbers and E-mail Addresses.
Related Articles
RSA Governance & Lifecycle Recipes: Dashboard - Reviews Summary 19Number of Views RSA Governance & Lifecycle Recipes: Dashboard - Admin Collector Summary 15Number of Views RSA Governance & Lifecycle ISO 27001 Dashboard Guide 18Number of Views RSA Governance & Lifecycle Advanced Dashboards Library Release Notes - Revision 1.0 37Number of Views RSA Governance & Lifecycle with RSA Authentication Manager Implementation Blueprint 23Number of Views
Trending Articles
RSA Release Notes for RSA Authentication Manager 8.8 RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide How to recover the Application and AFX after an unexpected database failure in RSA Identity Governance & Lifecycle RSA Release Notes: Cloud Access Service and RSA Authenticators RSA SecurID Software Token 5.0.2 for Windows Desktop displays message after reboot due to roaming profile: No token stor…