Certificate authentication and token validation checklist

Last Updated : Sep 07, 2021 |
Prolog information
The following procedures provide a worked example of using System Manager for signing a Certificate Signing Request (CSR) file. To complete the certificate authentication and token validation for Avaya Oceana®, maintain the sequence in the following table:
  • If an intermediate Certificate Authority (CA) signs your CSR, use the full certificate chain in a single .pem file.
  • If you have separate files, such as signed certificate, intermediate CA, and root CA, combine these files into a single .pem file before importing them into the keystore.
Note:
Ensure to maintain the following order of the certificates in the above instances in the .pem file:
  1. Signed certificate
  2. Intermediate certificate
  3. Root certificate
No.
Task
Notes
1
Get the AuthorizationService node and cluster information.
2
As a root user, to rename the current ssl directory, run the following command: mv /home/cust/ssl /home/cust/ssl4001
This step is required only for upgrades from version 4.0.0.1.
Ensure that the name of the folder containing the new certificates is different from /home/cust/ssl4001.
3
Create Certificate Signing Request for Avaya Oceana® authentication.
4
Get the .csr file signed.
5
Get identity token.
6
Import signed certificate for Avaya Oceana® authentication.
7
Retrieve the identity certificates.
8
Create Avaya Breeze® keystore.
9
Restart the relevant services.
See,