v3 API create_user does not use default_project_id
Bug #1662911 reported by
Doug Hellmann
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Designate |
Invalid
|
Undecided
|
Unassigned | ||
OpenStack Identity (keystone) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
The v3 call to create a user doesn't use the default_project_id argument except to validate it.
https:/
This caused problems when updating grenade to allow the ocata->pike tests to run, because the user was not set up with a default role as it had been under V2.
https:/
http://
http://
Changed in designate: | |
status: | Triaged → Invalid |
assignee: | Graham Hayes (grahamhayes) → nobody |
importance: | Critical → Undecided |
To post a comment you must log in.
v3 has always required authorization to be explicitly granted using a separate call, rather than being implied via a user-attribute. The intent is that user attributes may be set by the user themselves as a preference.
That said, setting the user password attribute acts as an administrative password reset, and we have a separate API for self-service password changes, so it's not exactly consistent.