OCSP, client certificate verification with chained CA

Marti, Ueli (Marin) Ueli.Marti at ch.glory-global.com
Fri Jan 7 07:24:53 UTC 2022

ok that makes sense.
Thank you for the feedback.

-----Original Message-----
From: nginx <nginx-bounces at nginx.org> On Behalf Of Maxim Dounin
Sent: Thursday, January 6, 2022 9:36 PM
To: nginx at nginx.org
Subject: Re: OCSP, client certificate verification with chained CA

CAUTION: This email originated outside the company. Do not click links or open attachments unless you are expecting them from the sender.


On Wed, Jan 05, 2022 at 03:33:29PM +0000, Marti, Ueli (Marin) wrote:

> Ok, good point thanks.
> However, it seems nginx accepts only one ssl_ocsp_responder instance.
> Or is there a syntax to specify multiple instances ?
> So this would need to be solved on the responder side which would need
> to be able to handle multiple CAs. Openssl ocsp doesn't seem to
> support that.
> Any chance for nginx to support multiple ssl_ocsp_responder instances
> in the future ?

Normally you shouldn't use ssl_ocsp_responder responder at all:
instead, certificate's Authority Information Access (AIA) extension is used to obtain appropriate OCSP responder address.

The ssl_ocsp_responder directive is something to be used to manually override information from AIA extension, either for testing or for complex configurations when you want to redefine OCSP server address for some reason.  If you do this, you can distinguish OCSP requests to different certificates based on the information in the requests, such as issuer name and issuer key hashes.  If the OCSP responder you use is not capable of doing this, consider removing the ssl_ocsp_responder directive, so nginx will use the AIA extension instead.

(Note well that using OpenSSL's builtin OCSP responder for anything but tests might not be a good idea.)

Maxim Dounin
nginx mailing list
nginx at nginx.org
This e-mail and any files attached are strictly confidential, may be legally privileged and are intended solely for the addressee. If you are not the intended recipient please notify the sender immediately by return email and then delete the e-mail and any attachments immediately. The views and or opinions expressed in this e-mail are not necessarily the views of Glory Ltd, Glory Global Solutions Limited or any of their subsidiaries or affiliates and the GLORY Group of companies, their directors, officers and employees make no representation about and accept no liability for its accuracy or completeness. You should ensure that you have adequate virus protection as the GLORY Group of companies do not accept liability for any viruses. Glory Global Solutions Limited Registered No. 07945417 and Glory Global Solutions (International) Limited Registered No 6569621 are both registered in England and Wales with their registered office at: Infinity View, 1 Hazelwood, Lime Tree Way, Chineham, Basingstoke, Hampshire RG24 8WZ, United Kingdom

More information about the nginx mailing list