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/08/17 08:14:40 UTC

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

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


   @sijie Thanks for your reply. I see the setting authenticationRefreshCheckSeconds=60 in broker.conf. But I still do not see broker disconnecting the client as described [here](https://pulsar.apache.org/docs/en/next/security-overview/). In my case connection remains although the token is already expired.
   
   I'm connecting via a pulsar proxy (deployed via Kubernetes helm chart) if that makes the difference.
   
   So, the current expected behaviour would be the client stops working, until [apache/pulsar-client-go#348](url) is ready (@wolfstudy  - yes, I'm surely interested in the feature)
   
   


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