12:03 p.m.
Those provider resources are always available under context of some
realm. So it will be always URL like
http://node1:8080/auth/realms/any-realm-name/your-provider-id/any-subcont...
This allows those providers to have access to current realm (the one
available through URL). If you have some logic, which is not coupled to
any realm, you just don't need to use RealmModel object. If you want to
have it available just for some specific realm (eg. master), it's
probably best to handle it programatically. Finally if you want shorter
URL and avoid realm context in the URL at all, you need to handle it at
proxy level though.
Marek
On 29/03/17 12:40, John D. Ament wrote:
Marek,
Thats very cool, thanks. We were wondering how to add custom modules,
this helps answer that. If we wanted to add a standard JAX-RS
resource (e.g. not realm specific) I'm assuming that can be done as well?
John,
Thanks for the pointer. We're in the same boat then.
On Wed, Mar 29, 2017 at 4:15 AM Marek Posolda <mposolda(a)redhat.com
<mailto:mposolda@redhat.com>> wrote:
Hi,
we plan to improve this in future version. For now, you may add custom
REST endpoint and do anything you want in it (eg. test if
infinispan is
running and infinispan has the expected count of nodes etc). For some
inspiration, you can try this:
https://github.com/mposolda/keycloak-session-info
Marek
On 29/03/17 01:44, John Bartko wrote:
> https://issues.jboss.org/browse/KEYCLOAK-1578
>
> As a load balancer operator, this defect means it is impossible to
> guarantee useful service delivery.
>
> I have been making use of /auth/realms/{realm} as a health check
URI. In
> cases where Infinispan gets hosed this health check can still
succeed, full
> disclosure.
>
>
> On Mar 28, 2017 4:46 PM, "John D. Ament" <john.d.ament(a)gmail.com
<mailto:john.d.ament@gmail.com>> wrote:
>
> Hi,
>
> I was wondering, from an operational standpoint, does Keycloak
provide any
> healthcheck mechanisms (e.g.a URI) that can be used to check if
the service
> is running?
>
> John
> _______________________________________________
> keycloak-user mailing list
> keycloak-user(a)lists.jboss.org <mailto:keycloak-user@lists.jboss.org>
> https://lists.jboss.org/mailman/listinfo/keycloak-user
> _______________________________________________
> keycloak-user mailing list
> keycloak-user(a)lists.jboss.org <mailto:keycloak-user@lists.jboss.org>
> https://lists.jboss.org/mailman/listinfo/keycloak-user