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
RSA Token Client returns error 40032 - R_TC_ERR_REGISTRATION_FAIL 15Number of Views How to determine the RSA Authentication Manager 8.x hardware platform 538Number of Views How to delete the RSA Authentication Manager 8.x virtual host Certificate Signing Requests (CSR) which show Pending/Inactive 1.41KNumber of Views Authentication for the Cloud Administration APIs 131Number of Views RSA DLP Enterprise Manager does not accept URLs ending with * or starting with * in transmission attributes 24Number of Views
Trending Articles
Troubleshooting RSA SecurID Access Identity Router to RSA Authentication Manager test connection failures RSA SecurID Software Token 5.0.2 Downloads for Microsoft Windows RSA Authentication Manager 8.9 Release Notes (January 2026) Quick Setup Guide - Passwordless Authentication in Windows MFA Agent for Active Directory RSA Authentication Manager 8.8 Setup and Configuration Guide
Don't see what you're looking for?