Open Stack

On 01/15/2013 03:42 PM, Dolph Mathews wrote:
> Per today's keystone meeting, I wrote a blueprint for the default domain
> solution, in order to provide an assumed scope for v2 API operations
> (which is not domain-aware), including authentication and validation, in
> the context of a deployment with v3 API users (which are domain-aware).
> 
>   https://blueprints.launchpad.net/keystone/+spec/default-domain

Hi Dolph. In the blueprint I see this:

The following pairs of calls would then be equivalent:

  GET /v2.0/users
  GET /v3/users?domain_id={default_domain_id}

  GET /v2.0/tenants
  GET /v3/projects?domain_id={default_domain_id}

  POST /v2.0/tokens {'auth': {'projectName': 'foobar'}}
  POST /v3/auth {'auth': {'projects': [{'name': 'foobar', 'domain_id':
'default'}]}

In the v3 API, can the user also leave off the domain_id? In other
words, are these two equivalent?

  GET /v3/users
  GET /v3/users?domain_id={default_domain_id}

Cheers,
-jay