OpenStack Identity (keystone)

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 on 2012-04-04

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	OpenStack Identity (keystone)	Fix Released	Undecided	Chmouel Boudjnah	OpenStack Identity (keystone) 2012.2 "folsom"

It should answer with something like this :

<?xml version="1.0" encoding="UTF-8"?>
<Error>
<Code>AccessDenied</Code>
<Message>Access denied</Message>
</Error>

instead of just the Response error header on invalid token.

Chmouel Boudjnah (chmouel) on 2012-04-04

Changed in keystone:
assignee:	nobody → Chmouel Boudjnah (chmouel)

Revision history for this message

OpenStack Infra (hudson-openstack) wrote on 2012-04-04: Fix proposed to keystone (master)

Fix proposed to branch: master
Review: https://review.openstack.org/6225

Changed in keystone:
status:	New → In Progress

Revision history for this message

OpenStack Infra (hudson-openstack) wrote on 2012-05-01: Fix merged to keystone (master)

commit ac3d31468da184abd7a68f5417822402aa69c199
Author: Chmouel Boudjnah <email address hidden>
Date: Wed Apr 4 17:30:51 2012 +0200

Exit on error in a S3 way.

    - Fixes bug 973433.
    - Add more debug logging.
    - Test xml output of s3_token.

Change-Id: Ibd0714bb6eeb75cfde614043fc7d062f584d0714

Changed in keystone:
status:	In Progress → Fix Committed

Joseph Heck (heckj) on 2012-05-20

Changed in keystone:
milestone:	none → folsom-1

Thierry Carrez (ttx) on 2012-05-23

Changed in keystone:
status:	Fix Committed → Fix Released

Thierry Carrez (ttx) on 2012-09-27

Changed in keystone:
milestone:	folsom-1 → 2012.2

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Bug watches keep track of this bug in other bug trackers.