When configuring fob-style token profile, the token is configured as PINPad-style when using RSA Authentication Manager 8.3 through 8.4 patch 1
Originally Published: 2019-05-22
Article Number
Applies To
RSA Product Set: SecurID
RSA Product/Service Type: Authentication Manager
RSA Version/Condition: 8.3 up to 8.4 patch 1
Issue
When using Authentication Manager Bulk Administration Utility (AMBA) command ATUA (Add Token to User Automatic), the distributed tokens use PINPad-style in spite of specifying a fob-style token profile.
For example a software token requests a PIN rather than allowing entry of fob-style PIN+tokencode:
Cause
Resolution
Related Articles
Database migration fails in test mode if RADIUS migration is completed first in RSA Authentication Manager 8.1 67Number of Views What are the specifications for RSA SecurID Standard Token Card Pinpad token and Key Fob tokens? 73Number of Views RSA Via L&G Supported OS Required Packages 6Number of Views AFX Server on a WildFly cluster fails to start with 'Cannot connect to RSA Identity Governance and Lifecycle. The watchdog… 238Number of Views Authentication Manager Console Access using CNAME or DNS alias fails with Redirect Logon Loop - ERR_TOO_MANY_REDIRECTS 5Number of Views
Trending Articles
Quick Setup Guide - Passwordless Authentication in Windows MFA Agent for Active Directory How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration 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?