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 RSA Authentication Manager 8.1 SP 1 patch 1 backups to a Windows Shared Folder are failing after software upgrade 246Number of Views Radius Client Authentication failed For PIN+Token profile (New PIN Mode) with Cisco Anyconnect VPN 125Number of Views How to configure an RSA Authentication Manager 8.1 server to accept a system-generated PIN when a token is in new PIN mode… 295Number of Views RSA SecurID Software Token Distribution to Android from RSA Authentication Manager 8.1 961Number of Views
Trending Articles
How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device How to replace the RSA Authentication Manager self signed console certificate with a signed certificate from Microsoft Act… RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide How to Request Access to the RSA Authentication Manager AMI for AWS via RSA Support
Don't see what you're looking for?