Ask Your Question

Revision history [back]

curl -H "X-Auth-Token: $AUTH_TOKEN" -H "Content-type: application/json" $OS_AUTH_URL/v3/auth/projects {"links": {"self": "http://x86.trystack.org:5000/v3/auth/projects", "previous": null, "next": null}, "projects": [{"is_domain": false, "description": "Auto created account", "links": {"self": "http://x86.trystack.org:5000/v3/projects/38db4610673545e58a99d7c0ea708174"}, "enabled": true, "id": "38db4610673545e58a99d7c0ea708174", "parent_id": null, "domain_id": "default", "name": "facebook665086733"}]}

This one is not obvious or published, but this is what Horizon does:

curl -H "X-Auth-Token: $AUTH_TOKEN" -H "Content-type: application/json" $OS_AUTH_URL/v3/auth/projects $OS_AUTH_URL/v3/auth/projects

{"links": {"self": "http://x86.trystack.org:5000/v3/auth/projects", "previous": null, "next": null}, "projects": [{"is_domain": false, "description": "Auto created account", "links": {"self": "http://x86.trystack.org:5000/v3/projects/38db4610673545e58a99d7c0ea708174"}, "enabled": true, "id": "38db4610673545e58a99d7c0ea708174", "parent_id": null, "domain_id": "default", "name": "facebook665086733"}]}

In general, without a scoped token, keystone operations can only be performed against the AUTH_URL. Thus, the enumeration of user specific information must be under OS_AUTH_URL/v3/auth