On login default the selected project by using default_project_id
Bug #1134766 reported by
Lin Hua Cheng
This bug report is a duplicate of:
Bug #1023502: Horizon does not use the default tenant.
Edit
Remove
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Dashboard (Horizon) |
Confirmed
|
Medium
|
Lin Hua Cheng | ||
Bug Description
In Keystone V3 API, the User object now includes default_project_id attribute.
On login, we should use this value if available when setting the Project scope for the user.
Keystone V3 API: https:/
| Changed in horizon: | |
| status: | New → Confirmed |
| Changed in horizon: | |
| assignee: | nobody → Lin Hua Cheng (lin-hua-cheng) |
| Changed in horizon: | |
| importance: | Undecided → Medium |
| milestone: | none → havana-1 |
Revision history for this message
| Lin Hua Cheng (lin-hua-cheng) wrote | #1 |
Revision history for this message
| Lin Hua Cheng (lin-hua-cheng) wrote | #2 |
To post a comment you must log in.
This would need to be postponed until keystoneclient has completely implemented the V3 authentication. When the user authenticate (POST /v3/auth/tokens), the default_project_id will be used automatically (if default_project_id exists in the user). We don't need to handle on horizon.
Right now keystoneclient V3 capability is still limited, we can only get the default_project_id by issuing another call to GET users. But the problem is this resource is only authrized for admin.