Disabling projects can lock the user out of the system
Bug #1067976 reported by
Adam Young
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Identity (keystone) |
Invalid
|
Undecided
|
Unassigned | ||
Bug Description
If you disable all the projects to which the currently logged in user has access, this user will be locked out of the system.
If you're the only admin, the only remedy is to edit the datbase by hand e.g.:
update keystone.tenant set extra = '{"enabled": true, "description": "-"}' where name = 'admin';
Reported in Horizon with https:/
Revision history for this message
| Joseph Heck (heckj) wrote | #1 |
| Changed in keystone: | |
| status: | New → Triaged |
Revision history for this message
| Dolph Mathews (dolph) wrote | #2 |
| Changed in keystone: | |
| status: | Triaged → Invalid |
To post a comment you must log in.
Can we use the bootstrapping client setup (i.e. configured shared-secret admin_token & mgmt-url) to re-enable the afflicted project that needs re-enabling?