After completing a certificate request and sending it to the Certificate Authority, the Certificate Authority issues a signed certificate response, which you import into the key database. After the signed certificate is imported, the existing self-signed certificate entry of the same alias is replaced.
To import a signed certificate response
The View Certificates and Private Keys dialog opens.
The Import Certificate and Keys dialog displays.
Note: You can click Help for a description of fields, controls, and their respective requirements.
The file should be a .p7 or .p7b file, containing the signed certificate and the corresponding certificate chain. It can also be a .cer or .crt file (base64 PEM file) with the signed certificate without the certificate chain.
The Available Entries table is displayed.
The Confirm dialog is displayed.
The signed certificate is imported into the key database and the self-signed certificate is replaced.
Note: To synchronize the policy engine with the key store immediately after you add or update a new certificate, restart the Federation Manager services. Otherwise, the changes to the key store are not available until the policy engine and key store synchronize. The amount of time for the policy engine and key store to synchronize depends on the configured frequency. You can modify database updates by adjusting the DBUpdateFrequencyMinutes parameter in the smkeydatabase.properties file.
| Copyright © 2010 CA. All rights reserved. | Email CA about this topic |