shouldn't be the same having a separated JPA project in charge of talking with our legacy database? Eventually what about  entitymanager null pointer exception? do you have an idea? should the jpa project be part of an ejb project?thanks Il Lunedì 7 Settembre 2015 19:29, Scott Rossillo <srossillo(a)smartling.com&gt; ha scritto: We'll publish an example of how to do this soon, but I'd recommend writing an API based provider on your legacy system instead of using a direct database connection from Keycloak. Sorry, doesn't exactly answer your question but it's a more elegant solution. On Mon, Sep 7, 2015 at 12:18 PM alex orl <alex_orl1079(a)yahoo.it&gt; wrote: I'm developing a keycloak user-federation-provider and i need to integrate it with the JPA persistence system in order to write on my legacy db and on the keycloak db.I read that Jboss WildFly already uses Hiberante 4.3 JPA, so i choose to follow this line for my project.Another requirement is to decouple the provider and the JPA model-mapping-project, so  my JPA model-mapping-project has to be deployed a separated jar file.Following the keycloak userguide i deploy the provider simply coping  the built jar project into the .../standalone/configuration/providers directory.The JPA model-mapping-project jar file is deployed into the Wildfly using the management console deployment section.Now i'm facing up to 2 problems:1) the user-federation-provider doesn't see the model-mapping-project  classes (throwing the ClassNotFoundException)2) if i simply copy the model-mapping-project.jar into the /standalone/configuration/providers directory, the fereration provider sees the classes but the EntityManager dependency injection does not work (NullPointerException) What the way i can solve this problem?Is there another way to deploy providers? and what about the jar and the depecency injection?ThanksRegards._______________________________________________ keycloak-dev mailing list keycloak-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/keycloak-dev