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

Posted to commits@pulsar.apache.org by GitBox <gi...@apache.org> on 2020/09/04 12:29:45 UTC

[GitHub] [pulsar] cuzyoucant commented on issue #7824: JWT token does not expire for opened connections

cuzyoucant commented on issue #7824:
URL: https://github.com/apache/pulsar/issues/7824#issuecomment-687112995


   Hi.
   
   I also ran into the same problem as @SergeyYakubov . Even with `authenticationRefreshCheckSeconds` set, the client just keeps on producing even though the token already expired. I think this problem only occurs when using a proxy, because in your test above @zymap i think you are using a direct connection between the client and broker. In my tests i was using the python client and not the go client though.
   
   The proxy even notices that the token is invalid (atleats it says that in the logs) but it just keeps on producing. And all the message that are produced can be consumed as well, so its not just a visual bug of some sort.
   
   I am happy to provide more info if you need it.
   Hope this helps!


----------------------------------------------------------------
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.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org