You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With the server configured as above, I tried to publish using z_put. I did not specific a client certificate in the z_put configuration. I expected the publish to fail.
However, the publish was successful. I think the server ignores the client_auth: true setting when using the quic protocol.
This fails as expected with transport set to 'tls'
Currently, mTLS is not implemented for QUIC, however, we are receiving more and more requests for it.
Thus we've started investigating how to implement it.
I think we should use this issue to keep track of it.
Currently, mTLS is not implemented for QUIC, however, we are receiving more and more requests for it. Thus we've started investigating how to implement it.
I think we should use this issue to keep track of it.
A related question. Is there any way for a publisher to get information about the identity of the subscriber - for example some information from the client certificate that was used in the mTLS?
Describe the bug
I followed the instructions here https://zenoh.io/docs/manual/tls/#mutual-authentication-mtls to configure mTLS authentication with the quic transport.
My router is configured like this
With the server configured as above, I tried to publish using z_put. I did not specific a client certificate in the z_put configuration. I expected the publish to fail.
However, the publish was successful. I think the server ignores the
client_auth: true
setting when using the quic protocol.This fails as expected with transport set to 'tls'
To reproduce
System info
The text was updated successfully, but these errors were encountered: