Error 7730: No private key in token
Symptom
"I have changed over to Token (RSA SID800) based security and now I get an error message stating that there is no private key on my token.I cannot login to my laptop as a result."
This error appears at boot logon after authenticating to your token, right before Windows is about to load. Cause
This error usually occurs when the private key on the token doesn’t match the public key used to encrypt the key file.
Ensure that:
1. GINA features are NOT enabled in Securedoc.
2. The certificate has the "Key Encipherment" attribute enabled.
3. The device has not gone into power-off or standby mode with the token still inserted.
Resolution
1. Ensure that the private key matches the key used to encrypt the key file. It may be also necessary to generate a new token/key to protect that device.
2. In SES: PROFILES--> right-click choose "MODIFY PROFILE"-->GENERAL OPTIONS-->GINA.
Push the new profile down to the device (It may be necessary to recover access using Challenge Response in order for SES to communicate with the device).
SECUREDOC STANDALONE: After logging into SecureDoc Control Center, select: CUSTOMIZE-->MODIFY OPTIONS-->GINA. Save changes and retry.
3. Please ensure the certificate contains "Key Encipherment", this can be verified as follows:
Double-click on the certificate, then choose the "Details" tab, then Under "Field" scroll down to "Key Usage".
4. If this error occurs after system power off (standby), please remove and insert the token again.
|
Custom Fields - Article ID: TS0111
- Error message or code: Error 0x7730: No private key in token
- Operating System: Windows
- Version: Affects all Versions
|