-
Notifications
You must be signed in to change notification settings - Fork 11
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
different secret per realm #1
Comments
Hi @jardakotesovec. We built this module for |
@jardakotesovec did you find a solution for this? If we could authenticate the client with JWT then we could use a common private key across multiple realms, but I couldn't get the keycloak nodejs adapter to work with the JWT's. |
@MumblesNZ Hi, were able to use original keycloak-nodejs-connect with this approach. With this strategy I can have multiple Keycloak instances with difference configurations and pick the correct one for each request. We are using this approach in production and works just fine. |
Add this.accessDenied to keycloakObject
Hi,
I have similar use case where I need to have multiple realms handled with keycloak. I am bit confused that this middleware seems to just have exactly same config for all keycloak instances except the realm name. How could I set different secret (`{credentials {secret: 'secret123' }}) for different realms?
I am wondering how you actually using that - you somehow imported same secrets in each realm? Or maybe I am missing something and is possible to set different secrets per realm?
Any feedback appreciated. Thanks!
The text was updated successfully, but these errors were encountered: