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 Workflow Policy 32Number of Views When trying to encrypt a new folder receiving an error: Encryption failed. FSSVC-33097 : Object access denied 2Number of Views SID800-based Token fails with the Error - “Authentication failed because tokencode could not be read from connected token”… 50Number of Views Generating a Software Token Profile Report for Authentication Manager 9Number of Views
Trending Articles
How a Multi-App Entitlement Collector (MAEDC) resolves entitlement relationships with accounts and groups collected by a M… RSA Governance & Lifecycle 8.0 Patch 10 Release Notes User Event Monitor Messages for Cloud Access Service (20601 - 38000) Authentication context not added / Context validation failed errors authenticating with RSA Authentication MFA Agent for A… RSA Governance & Lifecycle Data Processors: Basics
Don't see what you're looking for?