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

• Type: Bug
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 0.5.0
• Labels: pull-request-available
• Assignee: Guocheng Zhang
• Reporter: Guocheng Zhang
• Created: 26/May/20 12:09
• Updated: 28/Jul/21 11:38
• Resolved: 27/May/20 11:25

Description

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:

Issue Links

• links to: GitHub Pull Request #101
• links to: GitHub Pull Request #757