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
We already have a TLS CA and cert architecture set up, and would like to reuse that with nsq. This setup was all built out for Puppet, which uses the Subject of the cert to determine which machine is which. I'd like to see nsq pass the 'Subject CN' to the auth api, so we can determine what permissions a connection should have based on it's cert.
Combined with -tls-client-auth-policy require-verify, this would give us strong authentication without needing to maintain a separate list of shared secrets.
The text was updated successfully, but these errors were encountered:
We already have a TLS CA and cert architecture set up, and would like to reuse that with nsq. This setup was all built out for Puppet, which uses the Subject of the cert to determine which machine is which. I'd like to see nsq pass the 'Subject CN' to the auth api, so we can determine what permissions a connection should have based on it's cert.
Combined with -tls-client-auth-policy require-verify, this would give us strong authentication without needing to maintain a separate list of shared secrets.
The text was updated successfully, but these errors were encountered: