R_KM_KEY_get_security_obj_meta_data returned 10017
Originally Published: 2009-07-30
Article Number
Applies To
Issue
get_key call previously failed with error 10040
Resolution
After solving the error 10040, the 10017 error went away.
As an FYI, 10040 is a CA Certificate error. Make sure that the web server CA certificate is trusted by the RKM Client, and that the client cert's issuer CA is trusted by the web server.
Related Articles
How to determine the RSA Authentication Manager 8.x hardware platform 544Number of Views RSA Token Client returns error 40032 - R_TC_ERR_REGISTRATION_FAIL 17Number of Views How to configure RSA Validation Manager to obtain real-time certificate status from RSA Certificate Manager 31Number of Views Authentication for the Cloud Administration APIs 161Number of Views 'Request could not be handled' error reverting a Role that has been moved to a different Role Set in RSA Identity Governan… 56Number of Views
Trending Articles
How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device RSA-2026-10: RSA Authentication Manager Security Update for Third-Party Component Vulnerabilities RSA Authentication Manager 8.9 Release Notes (January 2026) Download RSA SecurID Access Cloud User Event audit logs using Cloud Administration REST API CLU RSA SecurID Desktop Token 5.0.3 for Windows Administrator's Guide
Don't see what you're looking for?