Upload OATH HOTP OTP Seed File fails with Admin Event "Authenticator(s) with serial number - [xxxxx] were not imported because their seed(s) were not base32 encoded
Article Number
Applies To
RSA Product/Service Type: Cloud Authentication Service
RSA Version/Condition: All
Issue
Admin Event Monitor captures - Authenticator(s) with serial number - [YUB23811755] were not imported because their seed(s) were not base32 encoded.
Cause
Resolution
Example of OATH HOTP seed file - BharathYubi.csv
Where :
2381175 - Token Serial Number
2RYCC3EJPDNBADNL3JSDAN5M2Z63UGKM - Secret Key "Base 32 encoded"
0 - Counter value
Upload OATH HOTP OTP Seed Files to the Cloud Authentication Service - OATH HOTP OTP Seed File should now import successfully
Admin Event Monitor
Workaround
The "20 Byte Hex" secret key generated by Yubikey Personalization Tool - d4 70 21 6c 89 78 da 10 0d ab da 64 30 37 ac d6 7d ba 19 4c in this case corresponds to 2RYCC3EJPDNBADNL3JSDAN5M2Z63UGKM "Base32 encoded" value
Related Articles
Duplicate Failure Counts in Unified OTP REST API Flow 19Number of Views Previously entered form values in RSA Via Lifecycle and Governance are not refreshed when navigating back in the form 21Number of Views Distribute One Software Token Using Dynamic Seed Provisioning 100Number of Views New Delivery Method for Token Seed Records 99Number of Views Dynamic Seed provisioning using QR Code 758Number of Views
Trending Articles
RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide RSA Authentication Manager Upgrade Process Artifacts to gather in RSA Identity Governance & Lifecycle Form approval node shows exception caught during script evaluation error in RSA Via Lifecycle and Governance RSA Release Notes for RSA Authentication Manager 8.8
Don't see what you're looking for?