If you do not have a key/certificate pair in the key database, you can import one from an existing .p12 or .pfx file.
In most cases, a certificate you import from the Import Certificate/Private Key dialog is treated as a trusted certificate. The exceptions are self-signed certificates. If Federation Manager identifies a V3 self-signed certificate as a CA certificate, then it is treated as a CA certificate despite the fact that the import is initiated from the Certificate/Private Key dialog. If a V3 self-signed certificate is not identified as a CA or if it is a V1 self-signed certificate, then it is treated as a trusted certificate.
To import a key/certificate pair from an existing file
The View Certificates and Private Keys dialog opens.
The Import Certificate/Private Key dialog displays.
Note: You can click Help for a description of fields, controls, and their respective requirements.
For a trusted certificate file in DER (binary) format, the file may contain one or more certificate entries. For a trusted certificate file in PEM (base 64) format, Federation Manager expects one certificate per file.
The Select Entries step is displayed with the Available Entries table.
For a trusted certificate file in DER (binary) format, the file may contain one or more certificate entries. For a trusted certificate file in PEM (base 64) format, Federation Manager expects one certificate per file.
The Entries to Import group box is displayed, showing the certificate information.
The certificate is imported into the key database.
| Copyright © 2010 CA. All rights reserved. | Email CA about this topic |