Skip to content
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

Allow to override authority used in hostname verification #8792

Closed
korthout opened this issue Feb 15, 2022 · 0 comments · Fixed by #8804
Closed

Allow to override authority used in hostname verification #8792

korthout opened this issue Feb 15, 2022 · 0 comments · Fixed by #8804
Assignees
Labels
kind/feature Categorizes an issue or PR as a feature, i.e. new behavior scope/clients-go Marks an issue or PR to appear in the Go client section of the changelog

Comments

@korthout
Copy link
Member

Is your feature request related to a problem? Please describe.
Similar to #8707, we can encounter this problem as well in the go-client.

Describe the solution you'd like
Allow to override the authority as well when using the go-client.

Describe alternatives you've considered
None

Additional context
Please have a look at the java-client's PR #8786

@korthout korthout added kind/feature Categorizes an issue or PR as a feature, i.e. new behavior scope/clients-go Marks an issue or PR to appear in the Go client section of the changelog Impact: Security labels Feb 15, 2022
@npepinpe npepinpe added this to Review in progress in Zeebe Feb 16, 2022
@npepinpe npepinpe self-assigned this Feb 16, 2022
@ghost ghost closed this as completed in 97046e3 Feb 18, 2022
Zeebe automation moved this from Review in progress to Done Feb 18, 2022
@KerstinHebel KerstinHebel removed this from Done in Zeebe Mar 23, 2022
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes an issue or PR as a feature, i.e. new behavior scope/clients-go Marks an issue or PR to appear in the Go client section of the changelog
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants