Avoid the default domain usage when the Domain is not specified in the project creation
Bug #1862802 reported by
Raildo Mascena de Sousa Filho
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Identity (keystone) |
Triaged
|
Wishlist
|
Unassigned |
Bug Description
We should issue an exception here since if a v3 call does not explicitly specify the domain_id in the entity, it should be using a domain scoped token. However, the current tempest heat tests issue a v3 call without this. This is raised as bug #1283539. Once this is fixed, we should remove the line below and replace it with an error. Ahead of actually changing the code to raise an exception, we issue a deprecation warning.
Since we can't change the current behavior of V3, because it will be api-breaking. We need to fix it in the Keystone microversion.
https:/
Changed in keystone: | |
status: | New → Triaged |
importance: | Undecided → Wishlist |
Changed in keystone: | |
assignee: | nobody → Vishakha Agarwal (vishakha.agarwal) |
Changed in keystone: | |
assignee: | Vishakha Agarwal (vishakha.agarwal) → nobody |
To post a comment you must log in.