Add OS-FEDERATION to scoped federation tokens

Bug #1351038 reported by Steve Martinelli
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Identity (keystone)
Fix Released
Medium
Steve Martinelli

Bug Description

Currently, when a federated user gets a token, it has an OS-FEDERATION section under 'user', which contains information about the idp and protocol.

However when the same user uses the unscoped token to get a scoped token, we should put the same information in there as well. This will help support revocation events for federated tokens, i.e. revoking all tokens based on IDP id.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to keystone (master)

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

Changed in keystone:
assignee: nobody → Steve Martinelli (stevemar)
status: New → In Progress
Dolph Mathews (dolph)
Changed in keystone:
importance: Undecided → Medium
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to keystone (master)

Reviewed: https://review.openstack.org/111070
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=9847ebd90ec450052cebbd55e5351be3fc05fcd5
Submitter: Jenkins
Branch: master

commit 9847ebd90ec450052cebbd55e5351be3fc05fcd5
Author: Steve Martinelli <email address hidden>
Date: Thu Jul 31 16:16:49 2014 -0400

    Add an OS-FEDERATION section to scoped federation tokens

    In this change, we add an OS-FEDERATION section to the user
    section in a scoped federation token. We currently do the same
    for unscoped tokens. This will also help with revocation events,
    specifically revoking tokens based on IDP id.

    Change-Id: Ibcb12a4a9db45351127458a96de1161de55d5a18
    Closes-Bug: #1351038

Changed in keystone:
status: In Progress → Fix Committed
Thierry Carrez (ttx)
Changed in keystone:
milestone: none → juno-3
status: Fix Committed → Fix Released
Thierry Carrez (ttx)
Changed in keystone:
milestone: juno-3 → 2014.2
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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