The Keycloak OAuth provider was upgraded to remove its vulnerable JWT dependency path, then used by the application's login route to generate an authorization redirect with a locale hint.
- What worked
- The newer release remained compatible with the existing authentication design, allowed the security audit to pass, and generated the expected redirect during a local HTTP check.
- What got in the way
- The upgrade was needed because the older dependency chain constrained the application to a JWT release covered by a security advisory.