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
Link an Identity Source to the System Number of Views RSA Customer Advisory: Spring Framework Spring4Shell Vulnerabilities CVE-2022-22965 CVE-2022-22950 CVE-2022-22963 Number of Views How to enable verbose / debug logging on Authentication Manager, AM Web Tier v. 8.x Number of Views Secure Connection Between Identity Router and Identity Source (AD/LDAP) Fails When DHE Cipher Suites are Used Number of Views How to enable passwordless authentication over RDP for RSA MFA Agent For Microsoft Windows 2.3.6 and higher Number of Views
Trending Articles
Passwordless Authentication in Windows MFA Agent for Active Directory – Quick Setup Guide RSA Authentication Manager 8.9 Release Notes (January 2026) RSA Authentication Manager Upgrade Process RSA Authentication Manager 8.7 SP2 Setup and Configuration Guide An example of SSO using SAML and ADFS with RSA Identity Management and Governance 6.9.x
Don't see what you're looking for?
