You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If we could leverage the existing support from OIDC that would be awesome. But I think it would require some refactoring on keycloak-authorization config. Do you agree, @sberyozkin ?
I can only see a 1:1 mapping between OIDC and keycloak-authorization tenants.
@pedroigor Hi Pedro, yeah, definitely, we can do it for the static tenants easily - by the time Keycloak Policy enforcer is called RoutingContext will already have a resolved tenant-id attribute. I reckon it would be reasonable to restrict it to the static tenants for now....
Description
Add multi-tenancy support to keycloak-authorization so that it can be used together with the oidc-multi-tenancy.
Implementation ideas
Configuration could be similar to the oidc-configuration:
The text was updated successfully, but these errors were encountered: