Support for multiple tenants in token scope in JSON
Bug #906442 reported by
Ziad Sawalha
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Identity (keystone) |
Fix Released
|
High
|
Ziad Sawalha |
Bug Description
In XML, we can return multiple <tenant/> tags when a token is scoped to multiple tenants. In JSON, however,we don't have support for that since we spec {"tenant": {}}.
Instead, we need to return
{"tenants": [{}, {}, {}]}
so we can return multiple tenants.
We will add this to the spec and keep the old "tenant" tag for compatibility until the next version of the API (tracked here https:/
Changed in keystone: | |
milestone: | none → essex-3 |
status: | New → Confirmed |
Changed in keystone: | |
importance: | Undecided → High |
Changed in keystone: | |
assignee: | nobody → Ziad Sawalha (ziad-sawalha) |
Changed in keystone: | |
status: | Fix Committed → Fix Released |
Changed in keystone: | |
milestone: | essex-3 → 2012.1 |
To post a comment you must log in.
Hey Ziad - a couple questions about this. How would a user create a multi-scoped token? The apis I'm aware of allow for either unscoped or singular scoping of tokens. Also, can you explain your use case that motivates this?