Imported CA not showing Root chain in KCA Admin Console
Originally Published: 2002-01-03
Article Number
Applies To
Issue
Took a CA certificate from one KCA installation (KCA1) over to the other KCA installation (KCA2) and signed it by the KCA2's Root CA. The new re-signed CA certificate got the entire chain. Then imported the re-signed CA certificate back into KCA1. Trusted KCA2's Root CA on KCA1. However even KCA2's Root CA is trusted on KCA1, when viewing this CA under "CA Operations" workbench through the Admin Server, the Certificate Chain still shows "Unknown".
Cause
Resolution
Related solution: Creating a CA hierarchy across multiple Sentry CA/Keon CA installations.
Related Articles
This certificate or its signing CA is not valid error when importing a certificate chain in RSA Authentication Manager 8.x… Number of Views Root CA certificate is required for activation error when importing a custom certificate signed by a known CA into Operati… Number of Views How to 'Trust' the RSA Authentication Manager Security Console Self-Signed Root CA certificate and prevent Cert warnings. Number of Views Error "keytool error: java.lang.Exception: Failed to establish chain from reply" when importing the SSP CA signed certific… Number of Views How to import a Root CA or public key Certificate into an Authentication Manager (or AMIS) java key store .jks with keytool Number of Views
Trending Articles
Downloading RSA Authentication Manager license files or RSA Software token seed records Unable to login to RSA Authentication Manager Security Console as super admin RSA Authentication Manager 8.9 Release Notes (January 2026) How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device Connection fails to Cloud Authentication Service when connecting through a proxy server from RSA Authentication Manager to…
Don't see what you're looking for?
