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.

Sign up for GitHub

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

Jump to bottom

[INLONG-158] nextWithAuthInfo2B status should be managed independently according to Broker #757

Closed
dockerzhang opened this issue Jul 28, 2021 · 0 comments
Closed

[INLONG-158] nextWithAuthInfo2B status should be managed independently according to Broker #757

dockerzhang opened this issue Jul 28, 2021 · 0 comments

Comments

@dockerzhang
Copy link
Contributor

In class BaseMessageConsumer.java , the nextWithAuthInfo2B parameter is set globally, but its purpose is to record whether the contacted Broker will perform authentication and authorization management during the next interaction. This parameter should be managed separately according to the Broker dimension:

JIRA link - [INLONG-158] created by gosonzhang
@dockerzhang dockerzhang added this to the 0.5.0 milestone Jul 28, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@dockerzhang