During the ignition process of a Linux-based IP Office server as a secondary or expansion server, the server generates a self-signed identity certificate. This identity certificate has limited value. You must replace it with one generated by the IP Office networks primary server or, if using third-party certificates, one from the same external CA.
Certificate Field |
Contents |
Notes |
Version |
V3
|
X.509 V3 format. |
Serial Number |
Large random number |
A unique serial number of up to 20 bytes. |
Signature Algorithm |
sha256RSA
|
– |
Issuer |
CN = <HostName>
O = Avaya Inc
OU = GCS
L = Basking Ridge
S = New Jersey
C = US
E = support@avaya.com
|
Where <HostName> is the hostname configured during ignition. |
Subject |
See above. |
The same as the Issuer. |
Issued By |
<HostName>
|
The <HostName> configured during ignition. |
Issued To |
<HostName>
|
The <HostName> configured during ignition. |
Valid From |
DD/MM/YY HH:MM:SS
|
Matches the server ignition UTC date and time minus 24- hours.
|
Valid To |
Approximately 2-years from the Valid From date and time. |
– |
Subject Alternative Name(s) |
None |
– |
Enhanced Key Usage |
None |
– |
Basic Constraints |
Subject Type=End Entity
Path Length Constraint = None
|
– |
Key Usage |
None |
– |
Subject Key Identifier |
Signature data |
– |
Public Key Algorithm |
RSA |
– |
Public Key |
Size 2048 bits |
– |
