[improve] Athenz auth provider supports Copper Argos #960
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
massakam
force-pushed
the
copper-argos
branch
from
659c3d0 to
84dbfcf
Compare
4 tasks
5 tasks
1 task
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation
As with the Java client (cf. apache/pulsar#19445), make the Athenz auth provider for the Go client support Copper Argos.
Modifications
Added new parameters
x509CertChainandcaCertto the Athenz auth provider. If the parameterx509CertChainis passed, the auth provider assumes that Copper Argos is used and presents the X.509 certificate to obtain a role token from ZTS. Existing users will not be affected by this change.Verifying this change