keystonemiddleware

Keystone V3 Should Be Used By Default Over V2

Bug #1336056 reported by Sam Leong
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
keystonemiddleware
Fix Released
Wishlist
Sam Leong
keystonemiddleware 1.1.0

Bug Description

Defaults keystone V3 for token validation as the service is migrating gradually over to keystone V3.
For those who are still using UUID token should default to V3 for online token validation, this will not impact PKI token.

Dolph Mathews (dolph)
Changed in keystonemiddleware:
importance: Undecided → Wishlist
status: New → Triaged
Sam Leong (chio-fai-sam-leong)
Changed in keystonemiddleware:
assignee: nobody → Sam Leong (chio-fai-sam-leong)
Revision history for this message
Dolph Mathews (dolph) wrote :

I actually fixed this in https://review.openstack.org/#/c/106819/ but apparently we don't have a bot to keep things in sync :(

Changed in keystonemiddleware:
status: Triaged → Fix Committed
milestone: none → 1.1.0
Revision history for this message
Sam Leong (chio-fai-sam-leong) wrote :

I got that. Thanks for the sync up!

Dolph Mathews (dolph)
Changed in keystonemiddleware:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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