Raw key size (bits) XXX does not match size defined by key class cipher
Originally Published: 2012-06-08
Article Number
Applies To
RKM Client Tool application
Issue
id=c6254392-21d2-4ec2-97d9-7c954fe33579
name=AES
mode=CBC
size=DefaultCipherSize[
effectiveSize=256
physicalSize=256
]
]
Resolution
Customer was trying to use the CREATE_NEW_KEY option of the RKM Client Tool application provided by RSA Customer Support. The Raw Key Data field was longer than the actual key size definition of the key class. Change the text to match the key class key size.
In a standard application you can also get this error if you try to create a key using a key size larger or different than the definition of the key class
Related Articles
Error: 'The server encountered the following unexpected condition: Error in RSA Federated Identity Manager: Error encounte… 9Number of Views 'ORA-12899: value too large for column "AVUSER"."T_EXPORT_ENTRIES"."OBJECT_NAME" (actual: XXX, maximum: 128)' error export… 72Number of Views 'ORA-01722: invalid number' or 'Non supported SQL92 token at position: XXX' errors in the aveksaServer.log when rendering … 74Number of Views Web Services updateReviewItems 'Entitlement XXX already in the same state' message does not display account name in RSA Id… 13Number of Views AFX Connectors remain in a Deployed state and 'Could not locate data file kahadb/db-XXX.log' error in RSA Identity Governa… 459Number of Views
Trending Articles
Downloading RSA Authentication Manager license files or RSA Software token seed records RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide Quick Setup Guide - Passwordless Authentication in Windows MFA Agent for Active Directory Mandatory Certificate Upgrade Required by 6th October 2025 for RSA MFA Agent for PAM, RSA MFA Agent for Apache, and Third … RSA Authentication Manager 8.9 Release Notes (January 2026)
Don't see what you're looking for?