"Primary Project *" field in "Create User" form should not be mandatory
Bug #1279505 reported by
Vahid Hashemian
This bug report is a duplicate of:
Bug #1285138: Horizon, python-keystoneclient treat "primary project" / tenantId differently.
Edit
Remove
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Dashboard (Horizon) |
Confirmed
|
Low
|
Vahid Hashemian | ||
Bug Description
Keystone V2 API for creating a user does not force a primary project to be provided for the user.
IMHO, Horizon should follow the same logic.
Users that are created through the API with no assigned primary project would not be able to login to Horizon and they would get the error "You are not authorized for any projects." which makes sense.
Then the user gets a primary project assigned if
- user record is updated with a primary project, or
- user is assigned its first role in a project
This behavior would match the API logic.
| Changed in horizon: | |
| assignee: | nobody → Vahid Hashemian (vahidhashemian) |
| Changed in horizon: | |
| status: | New → Confirmed |
| importance: | Undecided → Low |
| tags: | removed: create-user horizon mandatory primary-project v2 |
Revision history for this message
| Kanchan Gupta (kanchan-gupta1) wrote | #1 |
To post a comment you must log in.
It is a duplicate of bug-1285138.