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
Dynamic Seed provisioning using QR Code 754Number of Views How to verify the serial number of the certificate used for an LDAPS connection in RSA Authentication Manager 8.x 22Number of Views Distribute One Software Token Using Dynamic Seed Provisioning 269Number of Views New Delivery Method for Token Seed Records 96Number of Views Distribute One Software Token Using Dynamic Seed Provisioning 98Number of Views
Trending Articles
Quick Setup Guide - Passwordless Authentication in Windows MFA Agent for Active Directory RSA Authentication Manager 8.9 Release Notes (January 2026) Artifacts to gather in RSA Identity Governance & Lifecycle RSA Governance & Lifecycle 8.0.0 Administrators Guide RSA Governance & Lifecycle 8.0.0 Installation Guide
Don't see what you're looking for?