Hello I am trying to implement a userfederation-provider based on a jpa-connection. My approach was: According to an additional datasource-defintion for the federated DB in the standalone.xml <datasource jta="true" jndi-name=" *java:jboss/datasources/CCPDS*" pool-name="CCPDS" enabled="true" use-ccm="true"> <connection-url>jdbc:oracle:thin:@servername :1521:schemaname</connection-url> .. , I tried to register this datasource as an additional connectionJpa-entry in keycloak-server.json as follows: .. "connectionsJpa": { "default": { "dataSource": "java:jboss/datasources/CCPKCDS", "databaseSchema": "update" }*,* * "**FED**-**DB**": {* * "dataSource": "java:jboss/datasources/CCPDS"* * }* }, .. According to these configuration I hoped to be able to establish the appropriate entity manager by coding: // Get the appropriate entity manager from the KeycloakSession EntityManager em = session.getProvider(JpaConnectionProvider. *class*, "*FED**-**DB*").getEntityManager(); This did not work, indeed there is still only one (default) JpaConnectionProvider available in the session (JpaConnectionProviderList size is 1): Set<JpaConnectionProvider> *JpaConnectionProviderList* = session .getAllProviders(JpaConnectionProvider.*class*); My question is: isn’t it in principle possible to register a second jpaConnector additionally to the default one or is there something missing or wrong in my approach? Thanks for any help in advance. Best regards, Eduard Matuszak *Dr. Eduard Matuszak* Worldline, an atos company T +49 (211)399 398 63 M +49 (163)166 23 67 F +49(211) 399 22 430 *eduard.matuszak(a)atos.net* <eduard.matuszak(a)atos.net&gt; Max-Stromeyer-Straße 116 78467 Konstanz Germany *de.worldline.com* <http://worldline.com/de/1/Home.html> *worldline.jobs.de* <http://worldline.jobs.de> *facebook.com/WorldlineKarriere* <http://www.facebook.com/WorldlineKarriere> Worldline GmbH Geschäftsführer: Wolf Kunisch Aufsichtsratsvorsitzender: Christophe Duquenne Sitz der Gesellschaft: Frankfurt/Main Handelsregister: Frankfurt/Main HRB 40 417 * * * * * * * * L E G A L D I S C L A I M E R * * * * * * * * This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail by error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the internet, the Atos group liability cannot be triggered for the message content. Although the sender endeavors to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and shall not be liable for any damages resulting from any virus transmitted. * * * * * * * * L E G A L D I S C L A I M E R * * * * * * * * _______________________________________________ keycloak-user mailing list keycloak-user(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/keycloak-user

On Wed, 2015-11-11 at 14:12 +0100, Stian Thorgersen wrote: > At the moment when the provider is specified in keycloak-server.json > we only load that one provider. If you only need to use the > EntityManagerFactory within your user federation provider you don't > need a JpaConnectionProvider at all. Just create the > EntityManagerFactory within your UserFederationProviderFactory. I'm trying to do exactly that, but can't for the life of me get the EntityManagerFactory to create. It fails with: Caused by: javax.persistence.PersistenceException: No Persistence provider for EntityManager named XXXXX Before that, I also see this warning even if I explicitly pass the suggested provider as a property: 17:43:57,250 WARN [org.hibernate.ejb.HibernatePersistence] (default task-53) HHH015016: Encountered a deprecated javax.persistence.spi.PersistenceProvider [org.hibernate.ejb.HibernatePersistence]; use [org.hibernate.jpa.HibernatePersistenceProvider] instead. The persistence.xml is in META-INF. I also tried META-INF/classes/META- INF. My init code: private void lazyInit() { Map<String, Object> props = new HashMap<>(); props.put(AvailableSettings.PROVIDER, "org.hibernate.jpa.HibernatePersistenceProvider"); props.put(AvailableSettings.TRANSACTION_TYPE, "RESOURCE_LOCAL"); props.put("jboss.as.jpa.managed", "false"); emFactory = Persistence.createEntityManagerFactory("XXXXX", props); } This same persistence unit works just fine when bundled on it's own within a normal JEE EAR. Any idea what I'm doing wrong? Keycloak 1.7.0.Final -- Harold Campbell A farmer with extremely prolific hens posted the following sign. "Free Chickens. Our Coop Runneth Over."

On Wed, 2016-01-06 at 15:18 +0100, Stian Thorgersen wrote: > Are you deploying it as a module or by dropping it into > standalone/configuration/providers? The latter will pick up the > persistence.xml from Keycloak classloader so that's probably why it > doesn't work. Try deploying as a module instead as that's the only > way you can get full control of the classpath > I'm already deploying as a module. When I tried deploying into providers/ I didn't get the Persistence classes in my classpath. -- Harold Campbell <hcamp(a)muerte.net&gt; There's a little picture of ED MCMAHON doing BAD THINGS to JOAN RIVERS in a $200,000 MALIBU BEACH HOUSE!!