[keycloak-dev] Keycloak Client Provisioning Notifications.
Marek Posolda
mposolda at redhat.com
Fri Dec 4 07:03:42 EST 2015
We have events SPI. You can implement your own Events listener and
listen for events when:
- user register by himself (This is classic REGISTER event)
- admin creates new user in admin console (There is some admin event)
You can do EventListener provider, which will notify your application.
See some docs:
http://keycloak.github.io/docs/userguide/keycloak-server/html/events.html
http://keycloak.github.io/docs/userguide/keycloak-server/html/providers.html
Also take a look at providers/event-listener-.. in examples download
Marek
On 04/12/15 02:07, Thomas Darimont wrote:
> Hello there,
>
> are there any plans to provide a way to let client applications
> know of new users before they actually try to login?
>
> This could be used for triggering on-boarding mechanisms like e.g.
> preparing a user environment (e.g. a tenant) for a particular
> user.
>
> I was thinking of a mechanism like web-hooks, as github and many other
> services use in similar scenarios, where you could send a HTTP POST
> requests to the client application in case of
> a new user was registered in keycloak that was granted access to that
> particular application and potentially others as well.
>
> The POST request could contain some user data like:
> login, email, userid, client roles, perhaps for multiple clients etc.
> This would help client applications to associate a prepared
> environment with the actual user from keycloak.
>
> The intention is to keep an on-boarding experience fast as possible
> for the user by doing some preprocessing as early as possible.
>
> There is already a similar functionality to propagate logout events to
> client admin URL.
> Perhaps this could also be used for this - just send user created /
> user update / user deleted
> events to this endpoints as well.
> Perhaps with keeping track whether the clients acknowledged the
> updated via a HTTP 200 response-status with a retry with some back-off
> strategy otherwise.
>
> One often uses JMS topics for those scenarious but I think web-hooks
> would be a bit easier here.
>
> Cheers,
> Thomas
>
>
> _______________________________________________
> keycloak-dev mailing list
> keycloak-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/keycloak-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/keycloak-dev/attachments/20151204/e15ee35c/attachment.html
More information about the keycloak-dev
mailing list