1:24 a.m.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 01/20/2015 09:31 PM, John Sanda wrote:
For the dev environment, it looks like the keycloak appliance is
used. Does it use an embedded h2 database or something similar?
Will realms, user, and other auth info be persisted across
restarts?
Yes, it uses an embedded database and data is persisted across restarts.
What are the steps for creating realms/users? I am thinking about
after I do whatever is necessary to install/start the appliance and
after I start the metrics server.
The usual way to create a realm is by logging in as admin on the
Keycloak console (/auth) and creating a realm from there. It's also
possible to import a realm during the server startup by passing a
system property pointing to the realm's JSON file (which is what we do
in the start.sh).
To create a regular user, you can just self-register. Once you access
the Hawkular's web console, you'll be redirected to a login screen. On
this screen, there's a "register" link. You can use it to register
yourself. To change the roles, you'll need to login to the Keycloak
web console as admin and add roles to your user.
Is there a way to easily disable the authentication/authorization?
While it is not critical, I am thinking it might be nice if we
could do that in situations where we are debugging test failures
for instance.
Yes: just remove the authentication parts on the web.xml . Everything
should work fine. Not sure, though, what would happen if you try to
call a resource that is protected by the container via @RolesAllowed.
- - Juca.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQEcBAEBAgAGBQJUv1Q7AAoJECKM1e+fkPrXfFYIAJu06+Tg8suTU0pSWKbp8b1o
+ISU8htC3HXMMvXoE9dDqA3wQHPrChlN8sOwBciaQyLkv6RvM0EPfbxYQc6G6f25
2Ln0NM6tc7QVVgQYYcW+nIkbzWrX7cRpooPsqqM7KrWv7a5RUinhQWqNqky6VIPJ
oJQiwRUlpqzmeKMGhKtxWJwcEwyezKvVnwUp+c4VL1rSNxFJqqOItWfliWfxkS1s
Jzh/4WQt8QkoYtiuGxO3LwDsPNkfv/EQ3pYzWLYYNKKHmCzJNP8n+W+4P9QDZzLi
4MEBjcrwyRTi50x8mOUoPZKHdf3nh2MjVoHKdZaU36qnXejkf+i7zd372R+nogA=
=nkOZ
-----END PGP SIGNATURE-----