Error: 'HTTPS Error Returned:: java.lang.Exception: no trusted certificates found' in RSA Certificate Manager
Originally Published: 2006-05-30
Article Number
Applies To
Issue
Java application is using a .p7b file (PKCS#7) to load in their truststore do to a standard server authentication. That file contains the complete certificate chain and also the server certificate.
Cause
Resolution
Your client application needs to trust SubCA and/or RootCA ensuring that SSLCert will be chained to SubCA then trusted. In the symptom described above:
- The client application had SSLCert, SubCA, and RootCA in a single .p7b file, and the application was using this file as its truststore. The application was working fine.
- SubCA was then resigned (but not applied on the web server)
- The new SSLCert was exported with its full chain in a new .p7b file. This file then contained the new SubCA certificate.
- This new .p7b was then used by the application, and they had that symptom, because the application was doing a full certificate matching to allow the connection, and since SubCA certificate on the webserver was not the same as the one in the .p7b, the match failed, thus rejecting the connection.
Workaround
Related Articles
Splunk Enterprise - RSA Ready Implementation Guide Number of Views RSA Announces the March 2021 Release of RSA SecurID Access Number of Views Parsing Old Messages Against A New XML Number of Views Splunk Enterprise - SAML My Page SSO Configuration - RSA Ready Implementation Guide Number of Views 8071C G1 Re-Image Issue Number of Views
Trending Articles
How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device RSA SecurID software token .sdtid file fails to import into RSA SecurID Software Token 5.0 for Windows RSA Authentication Manager 8.9 Patches and Hotfixes Readme Download RSA SecurID Access Cloud User Event audit logs using Cloud Administration REST API CLU RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide
Don't see what you're looking for?
