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? 73Number of Views Database migration fails in test mode if RADIUS migration is completed first in RSA Authentication Manager 8.1 67Number of Views Generating a Software Token Profile Report for Authentication Manager 10Number of Views RSA Via L&G Supported OS Required Packages 6Number of Views Select Hardware Tokens for Provisioning 47Number of Views
Trending Articles
How to generate a PASSCODE for manual entry on a Ericsson R380 WAP phone RSA Authentication Manager Upgrade Process How to Understand the Difference Between RSA Authentication Manager Licenses and SecurID Token Assignments How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device RSA Authentication Manager 8.9 Release Notes (January 2026)
Don't see what you're looking for?