11 Select File in Base64 Format.
12 Specify the path and filename for the certificate.
Limit the filename to 8 characters. You can retain the .b64 extension or use the more general
.crt extension.
13 Click Save.
71.2.5 Installing the Certificate on the Server
After processing your CSRs, the Certificate Authority sends you a public certificate
(server_name.b64) file for each CSR. You might need to extract the private key from the public
certificate. The private key file might have an extension such as .pem or .pfx. The extension is
unimportant as long as the file format is correct.
If you used the Issue Certificate feature in ConsoleOne, as described in
Your Own Certificate," on page
and private key file (server_name.key).
Copy the files to any convenient location on each server. The location must be accessible to the
GroupWise agents that run on the server.
71.2.6 Configuring the Agents to Use SSL
To configure the agents to use SSL you must first enable them for SSL and then provide certificate
and key file information. For detailed instructions, see the following sections:
"Securing the Post Office with SSL Connections to the POA" on page 498
"Securing the Domain with SSL Connections to the MTA" on page 629
Securing Internet Agent Connections with SSL
Securing WebAccess Agent Connections with SSL
71.3 Trusted Root Certificates and LDAP
Authentication
LDAP authentication, as described in
GroupWise Users," on page
rootcert.der) located on your LDAP server. A trusted root certificate is automatically created
1121, it generated the public certificate file (server_name.b64)
Section 36.3.4, "Providing LDAP Authentication for
501, relies on the presence of a trusted root certificate (often named
Section 71.2.4, "Creating
Encryption and Certificates 1123
Need help?
Do you have a question about the GROUPWISE 7 - SECURITY ADMINISTRATION and is the answer not in the manual?