That’s exactly what I used, so before I can expose the keycloak to the world, I need to get into the node, call the script, restart server, login with the new admin, calling REST api to remove the admin, sounds like a lot of work?

Can we not config an init access token or something similar to smooth the thing, for our poor DevOps life?

Any help would be great!

Best,

Dong

Sent from Mail for Windows 10

From: Stian Thorgersen
Sent: 17 December 2015 15:41
To: Dong Xie
Cc: keycloak-user@lists.jboss.org
Subject: Re: [keycloak-user] out of box experiences and automation

From 1.7 you can add a admin user using the add-user script. See http://keycloak.github.io/docs/userguide/keycloak-server/html/server-installation.html#d4e136

On 17 December 2015 at 16:38, Dong Xie <xied75@gmail.com> wrote:

Dear all,

I wonder how do I work around needing to browse the web page and login with admin + admin to change the password? We are deploying keycloak in an automated flow thus no human interaction is expected.

Thanks very much for your help!

Best,

Dong

Sent from Mail for Windows 10

_______________________________________________
keycloak-user mailing list
keycloak-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-user