000024611 - How to allow certificate larger than 2Kb (2048 bytes) in RSA Key Manager Server 2.1.x?

Document created by RSA Customer Support Employee on Jun 16, 2016Last modified by RSA Customer Support Employee on Apr 21, 2017
Version 3Show Document
  • View in full screen mode

Article Content

Article Number000024611
Applies ToRSA Key Manager Server 2.1.3
RSA Key Manager Appliance 1.5
IssueHow to allow certificate larger than 2Kb (2048 bytes) in RSA Key Manager Server 2.1.x?
How to expand the AUTH_CERTIFICATE table to allow certificate larger than 2Kb?
com.rsa.edge.java.sql.SqlException: com.microsoft.sqlserver.jdbc.SQLServerException: String or binary data would be truncated.
 at com.rsa.edge.java.sql.DefaultPreparedStatement.executeUpdate(KeyManager:68)
java.sql.SQLException: ORA-12899: value too large for column "LOCAL"."AUTH_CERTIFICATE"."CERTIFICATE" (actual: 2210, maximum: 2048)
Unable to import large certificate
Size of certificate is too big or too large
ResolutionTo allow importing large certificate, run the following SQL statements on your database:

If you have a Microsoft SQL Server database:

use rkm;
alter table auth_certificate alter column certificate varchar(max)

If you have an Oracle database or are using RKM Appliance 1.5:

alter table auth_certificate add tmp_certificate varchar2(4000);
update auth_certificate set tmp_certificate = certificate;
alter table auth_certificate drop column certificate;
alter table auth_certificate rename column tmp_certificate to certificate;

For more details on how to connect to Oracle on RKM Appliance 1.5, follow the solution titled "How to connect to the Oracle instance in use by RKM Appliance?"
NotesRSA Key Manager Server 2.1.1, 2.1.2 and 2.1.3 schema have a limitation in the size of the certificate imported through the Admin Console.
Legacy Article IDa38814