The issuer certificate could not be found: this occurs if the issuer
certificate of an untrusted certificate cannot be found |
Oct 9 09:21:19:W: TLS: Issuer certificate is not available |
The public key in the certificate SubjectPublicKeyInfo could not be read |
Oct 9 09:21:19:W: X509v3 Certificate Validation failed: parse error on
public key |
The certificate is not yet valid: the notBefore date is after the current time |
Oct 9 09:21:19:W:TLS : X509v3 Certificate Validation failed: parse error on
notBefore |
The certificate has expired: that is the notAfter date is before the current
time |
Oct 9 09:21:03:W:TLS :X509v3 Certificate Validation failed: parse
error on notAfter |
The certificate common name doesn‘t match with server‘s IP address |
Oct 9 09:21:03:W: TLS: IP in certificate doesn't match
SAN |
The basicConstraints parameter is false for CA certificate |
Oct 9 09:22:08:W:TLS: BasicConstraints_CA is False for CA
cert |
The basicConstraints parameter is absent for CA certificate |
Oct 9 09:23:11:W:TLS:X509v3 Certificate Validation failed: basic
constraints absent for CA certificate %s |
The certificate notBefore field contains an invalid time |
Oct 9 10:11:35:W:TLS: Certificate validity is ahead of the
current time |
The certificate notAfter field contains an invalid time |
Oct 9 11:00:42:W:TLS: Certificate validity is ahead of the
current time |
The certificate chain could be built up using the untrusted certificates but the root
could not be found locally |
Oct 29 13:20:31.835 Error: Certificate chain doesn't end with any trusted certificate |
The basicConstraints path-length parameter has been exceeded |
Oct 9 11:03:52:W:TLS :X509v3 Certificate Validation failed: path
length constraints exceeded |
The certificate signature could not be decrypted. This means that the actual signature
value could not be determined rather than it not matching the
expected value, this is only meaningful for RSA keys |
Oct 9 11:03:52:W: X509v3 Certificate Validation failed: parse
error on signature algorithm |
Signature algorithm mismatch |
Oct 9 12:34:45:W:TLS: X509v3 Certificate Validation failed: signature algorithm
mismatch |
Signature key length is invalid |
Oct 9 12:34:45:W:TLS: X509v3 Certificate Validation failed:
signature algorithm key is too big |
TLS: In FIPS CC mode Minimum 2 certificates are needed excluding the trusted
certificate |
Oct 9 12:24:49:W:TLS: In FIPS CC mode Minimum 2 certificates are needed excluding the
trusted certificate |
During trusted CA import device failed to retrieve the size of the file |
Oct 9 11:03:52:W: TRUSTED CERT IMPORT: Failed to retrieve the
size of the certificate file |
During trusted CA import device failed to read the file from flash |
Oct 9 11:03:52:W: TRUSTED CERT IMPORT: Failed to read certificate
file from flash |
During trusted CA import, the size of the imported file was more than the maximum
supported |
Oct 9 11:03:52:W: TRUSTED CERT IMPORT: Certificate file size is
larger than supported 4096 bytes |
There is a maximum of 3 trusted certificates that can be imported. If user imports a
4th one a slot full audit log will be filed |
Oct 9 11:03:52:W: TRUSTED CERT IMPORT: Certificate slot is full.
Import failed |
The certificate index of the 3 supported certificate indexes can
be only 0,1 and 2. If for some reason the index is more than this an
audit log will be filed. |
Oct 9 11:03:52:W: TRUSTED CERT IMPORT: Certificate index is
invalid. Import failed |
The certificate length of the imported certificate was found to
be 0. |
Oct 9 11:03:52:W: TRUSTED CERT IMPORT: Certificate length is
invalid. Import failed |
The certificate data imported is encoded in
Base64-content-transfer encoding. If decoding this data fails audit
log will be filed for decode error |
Oct 9 11:03:52:W: TRUSTED CERT IMPORT: Certificate decoding
failed |
If certificate does not have valid fields, parse error will be
filed in the audit log |
Oct 9 11:03:52:W: TRUSTED CERT IMPORT: Certificate parsing failed
|