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

Multi tenant configuration: realmAuthServerUrlResolver #174

Closed
sbabych opened this issue Jan 28, 2024 · 1 comment
Closed

Multi tenant configuration: realmAuthServerUrlResolver #174

sbabych opened this issue Jan 28, 2024 · 1 comment

Comments

@sbabych
Copy link

sbabych commented Jan 28, 2024

Hello,

official keycloak-connect library has an issue related to the FrontendURL and the issuer validation.
Allow multiple auth-server-urls
Supporting different ISS when validating token

What do you think about idea to extend current Multi tenant configuration with new resolver: realmAuthServerUrlResolver
This resolver will change keycloak.grantManager.realmUrl and will help to bypass keycloak-connect library issues

Right now to achieve this I need to implement my own KeycloakMultiTenantService and override method:
get(realm: string): Promise<KeycloakConnect.Keycloak>;

Thank you!

@ferrerojosh
Copy link
Owner

You can make a PR for it and I can make a review, since you already extending and implementing your own.

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

2 participants