Hey Michalel, Based on my earlier experiences I can tell you that RealmResourceProvider SPI which you used does not distinguish realm resources and realms they will be actually pulled in. Its worth to remember that when RealmResourceProvider returns a null instead of valid resource object HTTP request will end up with 404 code. You need to combine both KeycloakContext [1] and configuration mechanism [2] to achieve final result. First will let you obtain current realm via getRealm method while second will bring flexibility through init(Scope) method call. For example if your config parameter is called LIID: @Override public void init(Scope config) { config.get("LIID", "some-fallback-value"); } This is all pseudo code, but I'm sure you will be able to find your way. [1]: https://github.com/keycloak/keycloak/blob/6.0.1/server-spi/src/main/java/... [2]: https://github.com/keycloak/keycloak-documentation/blob/6.0.1/server_inst... Cheers, Łukasz -- Code-House http://code-house.org On 30.05.2019 19:45, Michael Dailous wrote: