Gateway doesn't work after token refresh

[teon]

1. Pressing "Edit location settings" -> this already leads to the fact that the authentication token is different one.
2. After that restart defguard core service.
3. After that on the gateways you will start to see following logs:

defguard-gateway: [2024-11-20T10:38:24Z ERROR defguard_gateway::gateway] Couldn't retrieve gateway configuration from the core. Using gRPC URL: https://XXXXX:444/. Retrying in 10s. Error: status: Unauthenticated, message: "Invalid token", details: [], metadata: MetadataMap { headers: {"server": "nginx/1.22.1", "date": "Wed, 20 Nov 2024 10:38:24 GMT", "content-type": "application/grpc", "content-length": "0"} }

4. Then you update the authentication token to the new one, restart defguard-gateway service on the gateway node, everything starts to work again.

[voyvodov]

I think that generally the tokens should not refresh with every click on save or editing something in the location. Generate it once the location is created.
If needs to be refresh that must be manually and only if admin wants to do so (e.g. have a generate button)