Adds clarity to the usage of the authorisation token

As reported in LP#1277289, the usage of the authorisation
token is not clear in the instructions. It refers to a token
previously created but potentially leaves the user
confused as to which one to use. This patch adds the clarity
required and posts a link to the documentation section.

Change-Id: Ib16bd2770d4c4aac5292e9a3d2f25c2417e818f2
Closes-Bug: #1277289
backport: havana
This commit is contained in:
Rhys Oxenham 2014-02-18 14:22:39 +01:00
parent 3564b87a76
commit c2e6c077f3

View File

@ -15,17 +15,18 @@
<para>Typically, you would indicate a user and password to
authenticate with the Identity Service. At this point, however, we
have not created any users, so we have to use the authorization
token created in the previous section. You can pass this with the
token created in an earlier step, see <xref linkend="keystone-install"/>
for further details. You can pass this with the
<option>--os-token</option> option to the
<command>keystone</command> command or set the
<envar>OS_SERVICE_TOKEN</envar> environment variable. We'll set
<envar>OS_SERVICE_TOKEN</envar>, as well as
<envar>OS_SERVICE_ENDPOINT</envar> to specify where the Identity
Service is running. Replace
<userinput><replaceable>FCAF3E...</replaceable></userinput>
<userinput><replaceable>ADMIN_TOKEN</replaceable></userinput>
with your authorization token.</para>
<screen><prompt>#</prompt> <userinput>export OS_SERVICE_TOKEN=<replaceable>FCAF3E...</replaceable></userinput>
<screen><prompt>#</prompt> <userinput>export OS_SERVICE_TOKEN=<replaceable>ADMIN_TOKEN</replaceable></userinput>
<prompt>#</prompt> <userinput>export OS_SERVICE_ENDPOINT=http://controller:35357/v2.0</userinput></screen>
<para>First, create a tenant for an administrative user and a tenant