Closed didier-wenzek closed 1 year ago
The issue is addressed temporarily in this PR https://github.com/thin-edge/thin-edge.io/pull/2178. This is just a workaround. The real problem will be fixed in this ticket https://github.com/thin-edge/thin-edge.io/issues/2174
The Cumulocity mapper caches JWT tokens and refreshes them only on 401 authentication errors. This leads to an issue when these cached tokens are forwarded to the agent. The latter has currently no way to request a fresh token. The impacts are that all software update operations will fail till another operation triggers a token refresh.
The point here is to have a quick fix: the jwt token forwarded by the mapper to the agent must be a fresh token.
The main design issue (i.e. the mapper sending a JWT token to the agent with no way for the later to request a fresh one) will be fix independently.