R_KM_KEY_get_security_obj_meta_data returned 10017
Originally Published: 2009-07-30
Last Modified: 2023-10-06
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 Number of Views RSA Token Client returns error 40032 - R_TC_ERR_REGISTRATION_FAIL Number of Views 'Request could not be handled' error reverting a Role that has been moved to a different Role Set in RSA Identity Governan… Number of Views Authentication for the Cloud Administration APIs Number of Views enVision: Webserver crashes or will not stay started Number of Views
Trending Articles
How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device Reporting on RSA Authentication Manager 8.x users with On-Demand Token, a fixed passcode or a hardware/software token assi… How to Download OTP Token Seed Files from myRSA Anomalix idGenius - SAML Relying Party Configuration - RSA Ready Implementation Guide RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide
Don't see what you're looking for?
