Hi Stian, thanks for the quick reply! That sounds good, lack of backwards compatibility goes without saying :) So is the bootstrapping done in org.keycloak.services.resources.KeycloakApplication the right place to look at?


On Tue, Apr 15, 2014 at 10:30 AM, Stian Thorgersen <stian@redhat.com> wrote:
At some point we'll add a Java and REST api's for user management. This will also include being able to register listeners for user events (for example user created, user deleted, etc).

In the mean time I don't see any issues with using keycloak-model-jpa directly, especially not for read only. This API will quite likely change between versions, and we won't support any backwards compatibility. The "official" user management API once it's ready will be more stable, but I'm not sure when we'll have time to implement that.

----- Original Message -----
> From: "Nils Preusker" <n.preusker@gmail.com>
> To: keycloak-user@lists.jboss.org
> Sent: Tuesday, 15 April, 2014 9:22:44 AM
> Subject: [keycloak-user] Sharing users
> Hi, I have a question regarding user management and sharing access to the
> keycloak database between applications.
> While the keycloak admin console can be used to manage users, other
> applications may also need to access the user database. Is there a
> recommended way of accomplishing this?
> I've been experimenting with adding keycloak-model-jpa to my .war as a
> dependency and looking at the bootstrapping in
> org.keycloak.services.resources.KeycloakApplication. However, I wasn't able
> to get it to work yet and have the feeling that I might be going the wrong
> way here.
> Any hints?
> Cheers,
> Nils
> _______________________________________________
> keycloak-user mailing list
> keycloak-user@lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/keycloak-user