Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Keycloak multitenant service #194

Open
madicnikola opened this issue Dec 2, 2024 · 0 comments
Open

Keycloak multitenant service #194

madicnikola opened this issue Dec 2, 2024 · 0 comments

Comments

@madicnikola
Copy link

Issue Description

In multi-tenant mode, the logic for resolving instances in the keycloak-multitenant.service.ts has a flaw. When resolveAlways is enabled, the existing instance is not correctly updated with the new configuration (authServerUrl, secret).
More precisely the keycloak.grantManager resulting in errors: Cannot validate access token: Error: Grant validation failed. Reason: invalid token (wrong ISS) even when resolveAlways config is set to true

Steps to Reproduce

  1. Enable multi-tenant mode.
  2. Set resolveAlways to true.
  3. Observe that the instance is not updated properly with the latest configuration.

Expected Behavior

When resolveAlways is enabled, the existing instance should be updated with the new authServerUrl and secret.

Actual Behavior

The existing instance is not updated correctly, leading to outdated configurations.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant