Invalid X-Subject-Token results in HTTP 401 rather than 404
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Identity (keystone) |
Fix Released
|
High
|
Arvind Tiwari | ||
tempest |
Fix Released
|
Undecided
|
Morgan Fainberg |
Bug Description
While fixing https:/
e.g. all the below unit test try to make a head call after deleting/revoking x-subject-token and assumes that it will be unauthorized.
self.head(
In reality the above call creates another scoped token and auth passed with the new token, in that case 401 is not a correct test it should be 404 which is also aligned with docs https:/
test_deleting_
test_deleting_
test_deleting_
test_disabling_
test_group_
test_removing_
I found this issue with lots of V3 token related tests but as per Morgan Fainberg (morganfainberg) this also affecting V2 auth unit tests.
I am trying to fix V3 auth unit test issue as part of https:/
Changed in keystone: | |
assignee: | nobody → Arvind Tiwari (arvind-tiwari) |
summary: |
- Wrong unit tests for v3 token head calls + Invalid X-Subject-Token results in HTTP 401 rather than 404 |
Changed in keystone: | |
importance: | Medium → High |
milestone: | none → havana-rc1 |
tags: | added: grizzly-backport-potential |
Changed in keystone: | |
status: | New → In Progress |
Changed in keystone: | |
status: | In Progress → Fix Committed |
Changed in keystone: | |
status: | Fix Committed → Fix Released |
Changed in keystone: | |
milestone: | havana-rc1 → 2013.2 |
tags: | removed: grizzly-backport-potential |
Under the https:/ /wiki.openstack .org/wiki/ APIChangeGuidel ines it's "generally considered OK" to "change an error response code to be more accurate."