You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@inlong.apache.org by GitBox <gi...@apache.org> on 2021/07/28 11:38:24 UTC
[GitHub] [incubator-inlong] dockerzhang opened a new issue #757: [INLONG-158] nextWithAuthInfo2B status should be managed independently according to Broker
dockerzhang opened a new issue #757:
URL: https://github.com/apache/incubator-inlong/issues/757
<p>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:</p>
<p> <span class="image-wrap" style=""><img src="https://issues.apache.org/jira/secure/attachment/13004026/13004026_image-2020-05-26-20-06-46-124.png" style="border: 0px solid black" /></span> </p>
<i>JIRA link - <a href="https://issues.apache.org/jira/browse/INLONG-158">[INLONG-158]</a> created by gosonzhang</i>
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@inlong.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [incubator-inlong] dockerzhang closed issue #757: [INLONG-158] nextWithAuthInfo2B status should be managed independently according to Broker
Posted by GitBox <gi...@apache.org>.
dockerzhang closed issue #757:
URL: https://github.com/apache/incubator-inlong/issues/757
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@inlong.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org