You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@tubemq.apache.org by "Guocheng Zhang (Jira)" <ji...@apache.org> on 2020/05/26 12:19:00 UTC

[jira] [Assigned] (TUBEMQ-158) nextWithAuthInfo2B status should be managed independently according to Broker

     [ https://issues.apache.org/jira/browse/TUBEMQ-158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Guocheng Zhang reassigned TUBEMQ-158:
-------------------------------------

    Assignee: Guocheng Zhang

> nextWithAuthInfo2B status should be managed independently according to Broker
> -----------------------------------------------------------------------------
>
>                 Key: TUBEMQ-158
>                 URL: https://issues.apache.org/jira/browse/TUBEMQ-158
>             Project: Apache TubeMQ
>          Issue Type: Bug
>            Reporter: Guocheng Zhang
>            Assignee: Guocheng Zhang
>            Priority: Major
>         Attachments: image-2020-05-26-20-06-46-124.png
>
>
> 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:
>  !image-2020-05-26-20-06-46-124.png! 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)