[Authentication] Support chained authentication with same auth method name #9094
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
… name *Motivation* Chained authentication is a very useful mechanism for migrating a cluster from one authentication provider to the other authentication provider. However, Pulsar doesn't support configuring multiple authentication providers with same auth method name. For example, a Pulsar cluster was using standard JWT authentication initially. The users want to upgrade the Pulsar cluster to use an OAuth2 authentication mechanism. But both JWT and OAuth2 share the same authentication method name. This change improves the authentication logic to support chained authentication with same auth method name.
jiazhai
approved these changes
Dec 30, 2020
|
/pulsarbot run-failure-checks |
1 similar comment
|
/pulsarbot run-failure-checks |
codelipenghui
approved these changes
Dec 30, 2020
|
/pulsarbot run-failure-checks |
3 similar comments
|
/pulsarbot run-failure-checks |
|
/pulsarbot run-failure-checks |
|
/pulsarbot run-failure-checks |
…entication_providers
|
/pulsarbot run-failure-checks |
1 similar comment
|
/pulsarbot run-failure-checks |
|
@sijie There is a failed test, please take a look |
…entication_providers
…oviders' into allow_multiple_authentication_providers
|
@codelipenghui I have just pushed a change to fix the test. |
|
/pulsarbot run-failure-checks |
…entication_providers
…entication_providers
…oviders' into allow_multiple_authentication_providers
codelipenghui
pushed a commit
that referenced
this pull request
Jan 6, 2021
… name (#9094) *Motivation* Chained authentication is a very useful mechanism for migrating a cluster from one authentication provider to the other authentication provider. However, Pulsar doesn't support configuring multiple authentication providers with same auth method name. For example, a Pulsar cluster was using standard JWT authentication initially. The users want to upgrade the Pulsar cluster to use an OAuth2 authentication mechanism. But both JWT and OAuth2 share the same authentication method name. This change improves the authentication logic to support chained authentication with same auth method name. (cherry picked from commit c2a4e66)
codelipenghui
pushed a commit
that referenced
this pull request
Jan 7, 2021
… name (#9094) *Motivation* Chained authentication is a very useful mechanism for migrating a cluster from one authentication provider to the other authentication provider. However, Pulsar doesn't support configuring multiple authentication providers with same auth method name. For example, a Pulsar cluster was using standard JWT authentication initially. The users want to upgrade the Pulsar cluster to use an OAuth2 authentication mechanism. But both JWT and OAuth2 share the same authentication method name. This change improves the authentication logic to support chained authentication with same auth method name. (cherry picked from commit c2a4e66)
1 task
1 task
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
Chained authentication is a very useful mechanism for migrating a cluster from
one authentication provider to the other authentication provider. However,
Pulsar doesn't support configuring multiple authentication providers with same
auth method name.
For example, a Pulsar cluster was using standard JWT authentication initially.
The users want to upgrade the Pulsar cluster to use an OAuth2 authentication
mechanism. But both JWT and OAuth2 share the same authentication method name.
This change improves the authentication logic to support chained authentication
with same auth method name.