-
Notifications
You must be signed in to change notification settings - Fork 4.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
api/plugins: add tls-server-name arg for plugin registration #23549
Conversation
Build Results: |
CI Results: |
@@ -62,6 +63,7 @@ func (f *PluginAPIClientMeta) FlagSet() *flag.FlagSet { | |||
fs.StringVar(&f.flagCAPath, "ca-path", "", "") | |||
fs.StringVar(&f.flagClientCert, "client-cert", "", "") | |||
fs.StringVar(&f.flagClientKey, "client-key", "", "") | |||
fs.StringVar(&f.flagServerName, "tls-server-name", "", "") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we update any documentation for this?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I had trouble finding any existing documentation that called these out. Do you happen to know if any exist?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I didn't find anything either
If Vault is running in an ephemeral environment where nodes are often replaced and are randomly assigned IP addresses, it can be difficult to have IP SANs in server certs. By adding a TLS server name configurable we allow operators to register a plugin and specify the acceptable SAN for TLS verification.