S3_Token middleware is not coming back with proper s3 reply when unauthorized token or service is not available
Bug #973433 reported by
Chmouel Boudjnah
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Identity (keystone) |
Fix Released
|
Undecided
|
Chmouel Boudjnah |
Bug Description
It should answer with something like this :
<?xml version="1.0" encoding="UTF-8"?>
<Error>
<Code>
<Message>Access denied</Message>
</Error>
instead of just the Response error header on invalid token.
Changed in keystone: | |
assignee: | nobody → Chmouel Boudjnah (chmouel) |
Changed in keystone: | |
milestone: | none → folsom-1 |
Changed in keystone: | |
status: | Fix Committed → Fix Released |
Changed in keystone: | |
milestone: | folsom-1 → 2012.2 |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/6225
Review: https:/