update docs and templates to use tenant IDs (instead of names)

Bug #854228 reported by Dan Prince
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Identity (keystone)
Fix Released
Undecided
Dolph Mathews

Bug Description

As keystone now uses tenant IDs internally we should update docs, examples, and templates to use IDs instead of names for tenants.

For example. Instead of:

curl -d '{"passwordCredentials": {"username": "joeuser", "password": "secrete", "tenantId": "1234"}}' -H "Content-type: application/json" http://localhost:5000/v2.0/tokens

We should now use:

curl -d '{"passwordCredentials": {"username": "joeuser", "password": "secrete", "tenantId": "1"}}' -H "Content-type: application/json" http://localhost:5000/v2.0/tokens

** NOTE: using 1234 as a sample tenant name is probably bad since 1234 is really the name of the tenant although it also could be the ID.

Dan Prince (dan-prince)
Changed in keystone:
assignee: nobody → Dan Prince (dan-prince)
status: New → In Progress
Dolph Mathews (dolph)
Changed in keystone:
assignee: Dan Prince (dan-prince) → Dolph Mathews (dolph)
Revision history for this message
Openstack Gerrit (openstack-gerrit) wrote : A change has been merged to openstack/keystone

Reviewed: https://review.openstack.org/667
Committed: http://github.com/openstack/keystone/commit/e1deec3368aefdf93b4e4db43dd83553f386dfb3
Submitter: Jenkins
Branch: master

 status fixcommitted
 done

commit e1deec3368aefdf93b4e4db43dd83553f386dfb3
Author: Dolph Mathews <email address hidden>
Date: Wed Sep 28 13:48:00 2011 -0500

    Authenticating against non-existent tenant (fixed #859927)

    - Revised sampledata & management api to utlize object names exclusively (related to #849007)
      - Partial fix for bug #854228

    Change-Id: I026d3e543e183266ba023a961c9652f5ba9e34c6

Changed in keystone:
status: In Progress → Fix Committed
Joe Savak (jsavak)
tags: added: diablo-backport
Thierry Carrez (ttx)
Changed in keystone:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.