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 - Admin Collector Summary 15Number of Views RSA Governance & Lifecycle with RSA Authentication Manager Implementation Blueprint 24Number of Views RSA Governance & Lifecycle Integration: CA AutoSys Workload Automation Summary 17Number of Views RSA Governance & Lifecycle ISO 27001 Dashboard Guide 20Number of Views RSA Governance & Lifecycle Recipes: Dashboard - Reviews Summary 19Number of Views
Trending Articles
RSA Authentication Manager 8.7 SP2 Setup and Configuration Guide How to Download OTP Token Seed Files from myRSA Microsoft Entra ID External MFA - Relying Party Configuration Using OIDC - RSA Ready Implementation Guide RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide Download RSA SecurID Access Cloud User Event audit logs using Cloud Administration REST API CLU