Re: [keycloak-dev] Need advice on bootstrapping Keycloak
----- Original Message -----
From: "Stan Silvert" <ssilvert(a)redhat.com>
To: keycloak-dev(a)lists.jboss.org, "Juraci Paixão Kröhling"
<jpkroehling(a)redhat.com>
Sent: Friday, 18 July, 2014 2:29:54 PM
Subject: [keycloak-dev] Need advice on bootstrapping Keycloak
Hi guys,
My overall goal is to unite JBoss user-facing products via Keycloak
SSO. The first major task is make it as easy as possible to use
Keycloak with the WildFly web console. I have this working, but it
takes quite a bit of setup.
Ideally, there should be a simple switch in WildFly that says, "Use
Keycloak for web console", and it all just works.
So I'm looking for ideas on how to automate these setup tasks:
* Deploy Keycloak auth server and keycloak-ds.xml
Is the plan eventually to deploy Keycloak as an extension instead of a WAR? I reckon that
would solve a fair amount of issues. Could even go as far as creating KeycloakDS with a
persistent H2 db from within the subsystem if it's not available?
* Seed the database with an initial realm, user, roles, and two
applications
What about defining a boostrap-realm.json file. We already have mechanisms in place for
importing a file at startup, which is only imported if the realm doesn't already
exist.
* Create keycloak.json files or populate keycloak subsystem for the
two
apps.
Would be cool if you had an option to automatically create Keycloak subsystem definitions
for apps as they're creating in KC. Could have some sort of co-located option or
something.
Thanks in advance,
Stan
_______________________________________________
keycloak-dev mailing list
keycloak-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-dev