[branch-2.10] [fix] [auth] fix not forward compatible config saslJaasServerRoleTokenSignerSecretPath after cherry-pick #15121 #19971
Conversation
This file contains hidden or 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
Contributor
Author
|
/pulsarbot rerun-failure-checks |
codelipenghui
approved these changes
Apr 3, 2023
Contributor
Author
|
/pulsarbot rerun-failure-checks |
…ServerRoleTokenSignerSecretPath after cherry-pick apache#15121
poorbarcode
force-pushed
the
cherry_pick_15121
branch
from
9ccb09c to
105c9c7
Compare
Contributor
Author
|
Cherry-picked #14509 into |
Contributor
Author
|
/pulsarbot rerun-failure-checks |
nicoloboschi
pushed a commit
to datastax/pulsar
that referenced
this pull request
May 11, 2023
…ServerRoleTokenSignerSecretPath after cherry-pick apache#15121 (apache#19971) After cherry-picked apache#15121 into branch-2.10 to solve the issue sasl authentication failure, we will do a follow-up process to keep the new configuration `saslJaasServerRoleTokenSignerSecretPath` forward compatible: make this config optinal. (cherry picked from commit cef4f71)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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
This is A follow-up for cherry-pick #15121
After DIscuss: Cherry-pick #15121 into branch-2.10 to solve the issue sasl authentication failure, we will do a follow-up process to keep the new configuration
saslJaasServerRoleTokenSignerSecretPathforward compatible: make this config optinal.Modifications
Make the config
saslJaasServerRoleTokenSignerSecretPathoptinalDocumentation
docdoc-requireddoc-not-neededdoc-completeMatching PR in forked repository
PR in forked repository: