RSA FIM error: The public key present in the message did not match the public key present in the trusted keystore.
Originally Published: 2014-06-23
Article Number
Applies To
Issue
Following error in debug.log file
2014-06-19 11:28:25,597, (DSigHelper.java:548), TWFIM220V, , , , util.crypto.dsig.verify.error, java.lang.RuntimeException: Error code is not found: The public key present in the message did not match the public key present in the trusted keystore.
Cause
Resolution
Cut and past the data between X509Certificate tags into a text file and name the file certificate.cer. View the file in Windows and it will show the certificate data.
<KeyInfo>
<X509Data>
<X509IssuerSerial>
<X509IssuerName>CN=WS Enterprise CA1, DC=WS, DC=WSFGRP, DC=NET</X509IssuerName>
<X509SerialNumber>82469454475971740607926</X509SerialNumber>
</X509IssuerSerial>
<X509Certificate>
{cert data}
</X509Certificate>
</X509Data>
</KeyInfo>
The certificate should match what is stored in the JKS store. Use the following command to list the contents of the JKS store.
keytool -list -v -keystore truststore.jks
Related Articles
No X509 certificate in Client KeyStore Number of Views What is the difference between a client and server certificate? Number of Views FIM error 'Unable to load the keystore from keystore file location' Number of Views RSA Identity Governance and Lifecycle 7.1 Installation Guide Number of Views Downloading the Client Keystore for the AFX Server results in an HTTP 404 error in RSA Identity Governance & Lifecycle Number 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?
