OpenStack Identity (keystone)

S3 token should memcache the token validated in keystone

Bug #973681 reported by Chmouel Boudjnah on 2012-04-04

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	OpenStack Identity (keystone)	Invalid	Medium	Unassigned
	keystonemiddleware	Invalid	Medium	Unassigned

Currently we are making a request every time to keystone server for validating token, this should/could be cached.

Joseph Heck (heckj) on 2012-04-05

Chmouel Boudjnah (chmouel) on 2012-04-05

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

Chmouel Boudjnah (chmouel) on 2013-08-06

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

Revision history for this message

OpenStack Infra (hudson-openstack) wrote on 2013-11-08: Fix proposed to keystone (master)

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

Changed in keystone:
assignee:	nobody → Jeffrey Zhang (jeffrey4l)
status:	Confirmed → In Progress

Jeffrey Zhang (jeffrey4l) on 2013-11-08

Changed in keystone:
status:	In Progress → Confirmed
assignee:	Jeffrey Zhang (jeffrey4l) → nobody

Revision history for this message

Morgan Fainberg (mdrnstm) wrote on 2014-07-27:

S3token middleware is now in keystonemiddleware

Changed in keystonemiddleware:
status:	New → Confirmed
importance:	Undecided → Medium
Changed in keystone:
status:	Confirmed → Invalid

Revision history for this message

Tim Burke (1-tim-z) wrote on 2018-09-24:

s3token development has moved, first to swift3 and now to swift. If anyone's still interested, there's a patch up at https://review.openstack.org/#/c/603529/

Changed in keystonemiddleware:
status:	Confirmed → Invalid

This report contains Public information

Everyone can see this information.

You are

Subscribing...

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