Add User "Role" field to Update User Form
In the Identity -> Users Panel -> Create User Form, we can create a user without associating the user to any project (As per bug 1285138). In Update User Form, when we add/update the project for a user, there is no "Role" field to add/update the role of the user to the associated project.
This blueprint proposes, the addition of User "Role" field to the Update User Form so that it is consistent to the Create User Form and also provides an easy means to add/update the role of a user for the associated project.
In case no Project is selected in the Update User Form, the Role field will not be displayed. It will be visible only if the user is associated to any project.
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- tcs_openstack_group
- Direction:
- Needs approval
- Assignee:
- Preeti
- Definition:
- Obsolete
- Series goal:
- None
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
- David Lyle
Related branches
Related bugs
| Bug #1285138: Horizon, python-keystoneclient treat "primary project" / tenantId differently | Fix Released |
Sprints
Whiteboard
[tsufiev 24 Oct, 2014] Since any User can be assigned to more than one Project, with a given set of roles within each of those Projects (via Projects->Edit Users), IMO it would make sense to support the following UI in the UpdateForm: leave Primary Project to be single-select drop-down widget, but implement Role field as multiple-select widget - to show all the roles the user already has in a given project. Otherwise it's not obvious whether you overwriting existing set of roles or appending some new value to it.
[kgupta 7 Nov, 2014] Yes there can be different cases while assigning role to the user
Case-1 : Assigning Single role to a Project.
Case-2 : Assigning Multiple roles to a Project.
Case-1:The prototype for the Case-1 is ready.
Case-2:We can also define multiple roles to a project but currently this approach is not available in keystone api, so there will be a mismatch in horizon and keystone.
