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 Integration: Amazon Redshift Summary Number of Views RSA Governance & Lifecycle Recipes: Dashboard - Admin Collector Summary Number of Views RSA Governance & Lifecycle RACF Collector Datasheet Guide Number of Views RSA Governance & Lifecycle Zero Trust Dashboard Guide Number of Views RSA Governance & Lifecycle with RSA Authentication Manager Implementation Blueprint Number of Views
Trending Articles
How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device How to test RSA Identity Router (IDR) Secure Connector connectivity to the RSA ID Plus Cloud Access Service RSA SecurID Software Token for Microsoft Windows shows blank screen when asked to select a device where the token will be … RSA Governance & Lifecycle Generic Database Collector Guide RSA Authentication Manager 8.7 SP2 Administrator's Guide
