-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 01/29/2015 12:20 PM, Thomas Segismont wrote:
My last point was "The PR makes it impossible to install a
metrics
server without KC". I meant that if one needs to configure and run
a KC server in order to run a metrics server, then many potential
users will not even give it a try. Potential users here are admins
and production-focused developers who are working with combos like
Grafana/Graphite/collectd
Sorry for cutting the whole message to just this point, but before
talking about the other points, I just want to clarify one thing: the
admin does *not* need to deal with KC at all when trying things out.
To run a metrics server, one just runs the start.sh and Keycloak just
happens to be there as an implementation detail.
Once the admin is ready to bring things to production, then Keycloak
becomes a "concern", like any other backend would be (LDAP, SAML, ...).
Since the demo, I've been looking at how other projects are
integrating with Keycloak. The common scenario seems to be that their
Maven profiles build a "distribution" that is Wildfly + Keycloak +
WARs. So, the user just uncompresses this distribution package and has
everything ready (this is similar to what we had in GateIn).
Would this be a solution? I remember seeing somewhere that the goal is
not to be dependent on Wildfly[1], but not sure if this design goal is
still accurate.
[1]
https://developer.jboss.org/wiki/HighLevelRequirements
- - Juca.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQEcBAEBAgAGBQJUylr9AAoJECKM1e+fkPrXi+IH/1yx0shsoKHMDTuCXK5daemJ
riAofGmvrYelzfW7udiIuZXKMo4EtDge/Vocw296Uq1HibNb30x99WifwegCcLmv
10j8DdDc9ljupaS2Ej1D8RAGEOg6KdCrFj9V1tlhDbeAR9fXAeWqADZqH+5kjYbU
in7ayb0XvYJGYio8eLGdcMXt1vjy2fxArt1Y2u6AOdA8O2wyVMDkJ/Xs5tEPdkP0
BfRn8NOZdrlSDKd4qeG8qVtRQI006f/b+2hT6UnOM7gnc6QetYbBvVTHn0ODBwUA
mSj+HXrQJ6RR6MCUxkIr0Woii3SdA3ZsIDdZugAY0sGo8bgRgLVJ+zrpsgn23a8=
=Rcql
-----END PGP SIGNATURE-----