Access Manager allows you to manage centrally stored certificates used for digital signatures and data encryption. eDirectory™ resides on the Administration Console is the main certificate store for all of the Access Manager components. If you use Novell® Certificate Server™, you can continue to create certificates there and import them into Access Manager.
By default, all Access Manager components (Identity Server, Access Gateway, SSL VPN, and J2EE agents) trust the local Access Manager CA. However, if the Identity Server is configured to use an SSL certificate signed externally, the trust store of the embedded service provider for each component must be configured to trust this new CA.
Certificate management commands issued from a secondary Administration Console can work only if the primary console is also running properly. Other commands can work independent of the primary console.
You can create and distribute certificates to the following components:
Identity Server: Certificates allow you to provide secure authentication to the Identity Server and enable encrypted content from the Identity Server portal, via HTTPS. They also provide secure communications between trusted Identity Servers and user stores.
Liberty and SAML 2.0 protocol messages that are exchanged between identity and service providers often need to be digitally signed. The Identity Server uses the signing certificate included with the metadata of a trusted provider to validate signed messages from the trusted provider. For protocol messages to be exchanged between providers using SSL, each provider must trust the CA of the other provider. You must import the CA used by the other provider.
Access Gateway: Access Gateway uses server certificates and trusted roots to protect Web servers, provide single sign-on, and enable the product’s data confidentiality features, such as encryption.
SSL VPN: SSL VPN uses server certificates and trusted roots to secure access to non-HTTP applications.
J2EE Agent: The J2EE agent uses certificates to establish trust between the J2EE Agent and the Identity Server and for SSL between the J2EE server and the Identity Server.
To ensure the validity of X.509 certificates, Access Manager supports both Certificate Revocation Lists (CRLs) and Online Certificate Status Protocol (OCSP) methods of verification.
You can install and distribute certificates to the Access Manager product components and configure how the components use certificates. This includes central storage, distribution, and expired certificate renewal. Figure 23-1 illustrates the primary administrative actions for certificate management in Access Manager:
Figure 23-1 Certificate Management
Create the certificate and generate a certificate signing request (CSR). See Section 24.1, Creating Certificates.
Send the CSR to the external CA for signing.
A CA is a third-party or network authority that issues and manages security credentials and public keys for message encryption. The CA’s certificate is held in the configuration store of the computers that trust the CA.
Import the signed certificate and CA chain into the configuration store. See Section 24.5, Importing Public Key Certificates (Trusted Roots).
Assign certificates to devices. See Section 25.0, Assigning Certificates to Access Manager Devices.
See Section C.0, Certificates Terminology for information about certificate terminology.