'No certificate request was made' error when requesting a certificate on a smart card of SID800 against RSA Certificate Manager
Originally Published: 2009-10-21
Article Number
Applies To
RSA Certificate Manager 6.8
Issue
"No certificate request was made" error when requesting a certificate on a smart card of SID800 against RSA Certificate Manager
Cause
Resolution
Refer to the following solutions:
a12312 - How to set default for KCA enrollment to protect private key
a36012 - How to configure private key settings for Internet Explorer on Microsoft Vista
a34970 - How to force the key to be not exportable in Mozilla / FireFox
a31012 - How to set default Keon Certificate Authority OneStep certificate enrollment in order to protect the private key, effectively making certificate keys non-exportable
As of RCM 6.8 build 518, you do not need to edit the enrollment page as the key will be automatically flagged as non-exportable if "MS Base Smart Card CSP" is selected.
Notes
Related Articles
"A PIN is required for this token" error on RSA Authentication Manager 8.x when requesting an RSA SecurID software token f… Number of Views Unexpected error during command com.rsa.ucm.request.AddSelfServiceRequestCommand execution when requesting token via-Authe… Number of Views How to grant privileges to a user to edit one or more reports without providing Admin access in RSA Identity Governance an… Number of Views XudaInstanceOf failed to get xuda_cert_req object! result = 48 Number of Views Program Error: 'req-authorize.xuda: Line 518: [XrcNOTFOUND] unable to locate requested member or object. Unable to sign ce… Number of Views
Trending Articles
RSA Authentication Manager 8.9 Release Notes (January 2026) RSA announces the availability of the RSA SecurID Hardware Appliance 230 based on the Dell PowerEdge R240 Server How to troubleshoot Oracle database ORA-04030 errors in RSA Identity Governance & Lifecycle RSA Authentication Manager Upgrade Process Microsoft SQL Server Collectors can no longer connect to the SQL Server database after upgrade to Microsoft SQL Server 201…
Don't see what you're looking for?
