We have a new deployer in master that will be out in 2.2. You can create a provider in any Java EE deployment WAR, EAR, JAR, etc. The only requirement is that the ProviderFactory must be a pojo. You should be able to hook into CDI then.

On 9/8/16 12:36 PM, Jared Blashka wrote:

Is there a way to enable CDI support within custom Authenticator and Provider implementations?

I added the weld subsystem into our standalone.xml and added a beans.xml into the keycloak-server-subsystem WEB-INF directory, but the weld subsystem still wasn't recognizing the keycloak-server.war deployment as CDI-enabled (though other wars deployed on JBoss were recognized without issues).

I wanted to provide a default cache manager and annotate some of my authenticator/provider methods with @CacheResult to cache some fairly lengthy (but stable) data fetch operations.

I could manually persist this data in an infinispan cache, but using the annotations would be cleaner

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