Remove reference to built-in admin account from docs

This commit is contained in:
Stian Thorgersen 2016-01-13 09:02:52 +01:00
parent 2f88868e20
commit 62b90ee4e3
2 changed files with 10 additions and 21 deletions

View file

@ -81,6 +81,14 @@
<title>Version specific migration</title> <title>Version specific migration</title>
<section> <section>
<title>Migrating to 1.8.0</title> <title>Migrating to 1.8.0</title>
<simplesect>
<title>Admin account</title>
<para>
In previous releases we shipped with a default admin user with a default password, this has now been removed.
If you are doing a new installation of 1.8 you will have to create an admin user as a first step. This
can be done easily by following the steps in <link linkend="create-admin-user">Admin User</link>.
</para>
</simplesect>
<simplesect> <simplesect>
<title>OAuth2 Token Introspection</title> <title>OAuth2 Token Introspection</title>
<para> <para>

View file

@ -34,12 +34,6 @@
or: or:
<programlisting>keycloak-&project.version;/bin/standalone.bat</programlisting> <programlisting>keycloak-&project.version;/bin/standalone.bat</programlisting>
</para> </para>
<para>
Once the server is started log into the admin console at
<ulink url="http://localhost:8080/auth/admin/index.html">http://localhost:8080/auth/admin/index.html</ulink>
(username: <emphasis>admin</emphasis> and password: <emphasis>admin</emphasis>). Keycloak will then prompt you to
enter in a new password.
</para>
</section> </section>
@ -54,12 +48,6 @@
or: or:
<programlisting>&lt;WILDFLY_HOME&gt;/bin/standalone.bat --server-config=standalone-keycloak.xml</programlisting> <programlisting>&lt;WILDFLY_HOME&gt;/bin/standalone.bat --server-config=standalone-keycloak.xml</programlisting>
</para> </para>
<para>
Once the server is started log into the admin console at
<ulink url="http://localhost:8080/auth/admin/index.html">http://localhost:8080/auth/admin/index.html</ulink>
(username: <emphasis>admin</emphasis> and password: <emphasis>admin</emphasis>). Keycloak will then prompt you to
enter in a new password.
</para>
<para> <para>
To add Keycloak to other sever configurations (standalone.xml, standalone-ha.xml, etc.) start the server with To add Keycloak to other sever configurations (standalone.xml, standalone-ha.xml, etc.) start the server with
the desired server-config. If you are running the server in standalone mode run: the desired server-config. If you are running the server in standalone mode run:
@ -99,12 +87,6 @@ cd &lt;WILDFLY_HOME&gt;/bin
or: or:
<programlisting>keycloak-&project.version;/bin/standalone.bat</programlisting> <programlisting>keycloak-&project.version;/bin/standalone.bat</programlisting>
</para> </para>
<para>
Once the server is started log into the admin console at
<ulink url="http://localhost:8080/auth/admin/index.html">http://localhost:8080/auth/admin/index.html</ulink>
(username: <emphasis>admin</emphasis> and password: <emphasis>admin</emphasis>). Keycloak will then prompt you to
enter in a new password.
</para>
</section> </section>
</section> </section>
@ -114,9 +96,8 @@ cd &lt;WILDFLY_HOME&gt;/bin
Although the Keycloak Server is designed to run out of the box, there's some things you'll need Although the Keycloak Server is designed to run out of the box, there's some things you'll need
to configure before you go into production. Specifically: to configure before you go into production. Specifically:
<itemizedlist> <itemizedlist>
<listitem> <listitem>
Configuring Keycloak to use a production database. Configuring Keycloak to use a production database
</listitem> </listitem>
<listitem> <listitem>
@ -129,7 +110,7 @@ cd &lt;WILDFLY_HOME&gt;/bin
</itemizedlist> </itemizedlist>
</para> </para>
<section> <section>
<title>Admin User</title> <title id="create-admin-user">Admin User</title>
<para> <para>
To access the admin console to configure Keycloak you need an account to login. There is no built in user, To access the admin console to configure Keycloak you need an account to login. There is no built in user,
instead you have to first create an admin account. This can done either by opening <ulink url="http://localhost:8080/auth">http://localhost:8080/auth</ulink> instead you have to first create an admin account. This can done either by opening <ulink url="http://localhost:8080/auth">http://localhost:8080/auth</ulink>