Marco Aurelio Caldas Miranda

The query returned session_id | expired | connection_limit | open_connections | closed_connections | open_worker_id | closed_worker_id -- | -- | -- | -- | -- | -- | -- s_pD1b6GA9KN...

> Did these workers eventually reconnect? Yes. To my surprise they are actually active. I thought that because we run workers on Kubernetes, they had been replaced during an upgrade...

So I thought the connections with state `connected` could be of special interest public_id | worker_id | connection_id | state -- | -- | -- | -- s_bLnLrQyYjZ | w_sy0swTMhaT...

Hi @tmessi, anything else I can check that would help you understand this issue. If not, I'm thinking of manually removing those sessions again. I haven't noticed any new sessions...

Hi @tmessi, > It would require a specific timing of events in which the worker is unable to report to the controller and then resumes communication. While you were experiencing...

Just to let you know, we are still seeing `sendWorkerStatus` errors but it seems the worker is handling it well, i.e. canceling the sessions, which I can see in the...

Probably should ask on https://discuss.hashicorp.com/ first

Hi @xingluw, just to clarify, is [this](https://developer.hashicorp.com/vault/docs/auth/jwt/oidc-providers/google) not what @praneshkumarkn1 is asking for?

🤭 Wrong project!

Hi @praneshkumarkn1 , For the time being, you'll need something in between Boundary and Google API that can expose the groups as OIDC claims, e.g. DeX