Recently we noticed that OCSP is not working for SSL configurations that are setup for dual certs. On startup, there's a warning about failing to configure OCSP for the set of certificates.
Currently we're running ATS 7.1.3(with the patch from #3004) with OpenSSL 1.1.0g. I've verified this also occurs on 7.1.1 with OpenSSL 1.0.2l
We have a configuration like this in ssl_multicert.config:
ssl_cert_name=sub.domain.com.rsa,sub.domain.com.ecdsa
On load, we see these messages in the logs regarding these certs:
traffic_server[57147]: {0x2aaaaaecc260} NOTE: cannot get issuer certificate from sub.domain.com.rsa,sub.domain.com.ecdsa
traffic_server[57147]: {0x2aaaaaecc260} WARNING: fail to configure SSL_CTX for OCSP Stapling info for certificate at sub.domain.com.rsa,sub.domain.com.ecdsa
traffic_server[57147]: {0x2aaaaaecc260} NOTE: certificate already initialized for sub.domain.com.rsa,sub.domain.com.ecdsa
traffic_server[57147]: {0x2aaaaaecc260} WARNING: fail to configure SSL_CTX for OCSP Stapling info for certificate at sub.domain.com.rsa,sub.domain.com.ecdsa
traffic_server[57147]: {0x2aaaaaecc260} WARNING: previously indexed ',sub.domain.com' with SSL_CTX 0x9d, cannot index it with SSL_CTX #158 now
Requests querying for certificate status for that domain, also result in an error message (for each request)
traffic_server[57147]: {0x2aaab35a8700} ERROR: ssl_callback_ocsp_stapling: failed to get certificate information
(can be triggered by "curl --cert-status ...")
Recently we noticed that OCSP is not working for SSL configurations that are setup for dual certs. On startup, there's a warning about failing to configure OCSP for the set of certificates.
Currently we're running ATS 7.1.3(with the patch from #3004) with OpenSSL 1.1.0g. I've verified this also occurs on 7.1.1 with OpenSSL 1.0.2l
We have a configuration like this in ssl_multicert.config:
ssl_cert_name=sub.domain.com.rsa,sub.domain.com.ecdsaOn load, we see these messages in the logs regarding these certs:
Requests querying for certificate status for that domain, also result in an error message (for each request)
(can be triggered by "curl --cert-status ...")