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
What are the specifications for RSA SecurID Standard Token Card Pinpad token and Key Fob tokens? 67Number of Views Smart Card Logon certificate not accepted 36Number of Views Login fails with an 'Internal Server Error' when using SiteMinder SSO to log into RSA Identity Governance & Lifecycle 73Number of Views Differences to be aware of when configuring RSA SecurID Access Cloud IdP vs IDR IdP 79Number of Views Authentication Manager 8.x Deployment on Cloud Platform Fails When Configuring Network Settings 15Number of Views
Trending Articles
RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide RSA Release Notes for RSA Authentication Manager 8.8 RSA Authentication Manager 8.9 Release Notes (January 2026) Supported On-Demand Authentication (ODA) SMS providers for use with RSA Authentication Manager 8.x Deploying RSA Authenticator 6.2.2 for Windows Using DISM
Don't see what you're looking for?