000014464 - Cert-C: Can't use private key imported from .sst for signing

Document created by RSA Customer Support Employee on Jun 15, 2016Last modified by RSA Customer Support Employee on Apr 21, 2017
Version 2Show Document
  • View in full screen mode

Article Content

Article Number000014464
Applies ToRSA BSAFE Cert-C
Microsoft Windows
IssueCert-C: Can't use private key imported from .sst for signing
After importing a certificate from a .sst (Microsoft Serialized Certificate Store) file, calling C_WriteSignedDataMsg() fails with error 1800 (E_NOT_FOUND).
The Cert-C status log shows the following when C_WriteSignedDataMsg() is called:
C:\cygwin\home\build\tag\certc-2_8-fcs-test_freeze-7\CERTC\certc\package_source\win32pkg\certc\provider\db\capi\capiprov.c(2575) : E_PROVIDER : CSP related error (NTE_BAD_KEYSET)
CauseA .sst (Microsoft Serialized Certificate Store) file only contains certificates, not private keys.
ResolutionThe private key should either be generated by the application or imported from a PKCS #12 file.
Legacy Article IDa46512

Attachments

    Outcomes