TLS Peer Verification: Do not fail if client certificate does not contain expected value for extended key usage extension #10002
-
TLS Peer Verification: Do not fail if client certificate does not contain expected value for extended key usage extension In order to enable TLS Peer Verification, I have added to Rabbitmq config (apart from TLS encryption), this config to force rabbitmq to fail if client does not present a valid certificate signed by a trusted authority.
On client side, I have added to configuration the usage a certificate when establishing connection to Rabbitmq. This certificate has on its extension 'Extended Key Usage' set to TLS Web Server Authentication. I do have this error when client connects to Rabbitmq :
From what I understood, I have this error because the client presents a certificate with extension 'Extended Key Usage' set to TLS Web Server Authentication instead of TLS Web Client Authentication. Set this restriction as an optionIs it possible to have an option that let us control this validation ? The main verification is that the presented certificate is signed by a trusted authority right ? Alternative SolutionOption could be like: Additional context(For some reason, my company does not deliver certificates with that value of extension.) |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
RabbitMQ does not implement TLS. Erlang/OTP does. I believe how the extended key usage extensions are treated is covered by one of the PKI RFCs. It's not something that a TLS implementation can change because it would be convenient in some cases. |
Beta Was this translation helpful? Give feedback.
RabbitMQ does not implement TLS. Erlang/OTP does. I believe how the extended key usage extensions are treated is covered by one of the PKI RFCs. It's not something that a TLS implementation can change because it would be convenient in some cases.