-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
Add refresh authentication command in broker #9064
Conversation
--- (If this PR fixes a github issue, please add `Fixes #<xyz>`) Fixes #<xyz> (or if this PR is one task of a github issue, please add `Master Issue: #<xyz>` to link to the master issue) Master Issue: #<xyz> *Motivation* Describe here the context, and why you're making that change. What is the problem you're trying to solve. *Modifications* Describe the modifications you've done. *Verify this change* Please pick either of following options. - This change is a trivial rework / code cleanup without any test coverage. - This change is already covered by existing tests, such as *(please describe tests)*. - This change added tests and can be verified as follows: *(example:)* - *Added integration tests for end-to-end deployment* - *Extended integration test for recovery after broker failure*
pulsar-client/src/main/java/org/apache/pulsar/client/impl/auth/oauth2/AuthenticationOAuth2.java
Outdated
Show resolved
Hide resolved
...client/src/main/java/org/apache/pulsar/client/impl/auth/oauth2/AuthenticationDataOAuth2.java
Outdated
Show resolved
Hide resolved
8621434
to
c469ca3
Compare
/pulsarbot run-failure-checks |
/pulsarbot run-failure-checks |
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.
A couple of questions:
- Don't we need to change the client authentication providers to support fresh authentication?
- Can you please add tests and integration tests to ensure the change is implemented correctly?
@sijie sorry for the delay. This PR's goal is to address the issue that pulsar will disconnect the client if the token expired. I improve the expiration token test to include my case. |
/pulsarbot run-failure-checks |
2 similar comments
/pulsarbot run-failure-checks |
/pulsarbot run-failure-checks |
/pulsarbot run-failure-checks |
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.
@zymap well done!
* Add refresh authentication command in the broker --- **Motivation** Some authentication provider is using cached authentication data. Until redoing the 'getAuthData' then it will provide the new auth data. So I add a refresh command and do the refresh authentication data provider when received the command. **Verify this change** Existent tests can pass. (cherry picked from commit 373948e)
* Add refresh authentication command in the broker --- **Motivation** Some authentication provider is using cached authentication data. Until redoing the 'getAuthData' then it will provide the new auth data. So I add a refresh command and do the refresh authentication data provider when received the command. **Verify this change** Existent tests can pass. (cherry picked from commit 373948e)
* Add refresh authentication command in the broker --- **Motivation** Some authentication provider is using cached authentication data. Until redoing the 'getAuthData' then it will provide the new auth data. So I add a refresh command and do the refresh authentication data provider when received the command. **Verify this change** Existent tests can pass. (cherry picked from commit 373948e)
Motivation
Some authentication provider is using cached authentication data. Until
redoing the 'getAuthData' then it will provide the new auth data. So
I add a refresh command and do the refresh authentication data provider
when received the command.
Verify this change