Hi Team,
We're facing a critical issue with our Keycloak 18.0.18 deployment on a RHEL 9 VM, which uses Azure MySQL with Azure AD authentication. As you know, the managed identity token for Azure MySQL expires after 24 hours.
We need to implement an automated token refresh mechanism that updates the token 5 minutes before its expiration, without requiring a Keycloak restart.
Our current setup is as follows:
We urgently require a solution to prevent service interruption due to token expiration. Please provide guidance on the most efficient and reliable approach to implement this token refresh, preferably involving a custom Keycloak module or any other method that avoids Keycloak restarts.
Your immediate assistance is greatly appreciated, as this needs to be resolved as quickly as possible.
Thanks,
Akansh