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
I have been trying (unsuccessfully) to build a client that uses TLS client authentication via X.509 certificates. After digging around the code I think that right now only server authentication via X.509 is possible and client authentication is restricted to SASL. Is that the case or am I missing something?
Could this feature be considered for a future release?
Thanks!
The text was updated successfully, but these errors were encountered:
Thanks @fjcrabiffosse!
Yes you are correct - client auth is currently restricted to SASL.
I have to do some digging in the TLS layer soon for the addition of websocket support so while I'm down there I will take a look at how much work this would be.
I have been trying (unsuccessfully) to build a client that uses TLS client authentication via X.509 certificates. After digging around the code I think that right now only server authentication via X.509 is possible and client authentication is restricted to SASL. Is that the case or am I missing something?
Could this feature be considered for a future release?
Thanks!
The text was updated successfully, but these errors were encountered: