I had the same problem and ended up creating a subclass which first tries a custom location and falls back to the original implementation. Spring obtains the value from JNDI to enable external configuration.

I actually wrote about this a while ago. I'm happy to add the same functionality to the adapter as it could be useful to others as well.

On Sep 28, 2015 23:23, "Andrzej Goławski" <andipansa@gmail.com> wrote:

Hi,

I've started to use keycloak with spring security and found that the name and location of keycloak.json file was hardcoded. IMO it would be better to allow injection of the configuration file name via constructor in AdapterDeploymentContextBean by developer. Thus, I would be able to use different keycloak configurations with different spring profiles. What do you think about it?

Best Regards,
Andrzej

_______________________________________________
keycloak-dev mailing list
keycloak-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-dev