Unauth context doesn't provide all X-xxxx fields to context

Bug #1497639 reported by John Wood
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Barbican
Fix Released
Critical
John Wood

Bug Description

The current unauth context doesn't take all relevant X-xxxx fields (including the X-User-Id) from the HTTP header and place them into the Barbican context object. The means there is no way to test user-based features like ACL using the unauth context.

John Wood (john-wood-w)
Changed in barbican:
assignee: nobody → John Wood (john-wood-w)
importance: Undecided → Critical
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to barbican (master)

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

Changed in barbican:
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to barbican (master)

Reviewed: https://review.openstack.org/225455
Committed: https://git.openstack.org/cgit/openstack/barbican/commit/?id=a80c32587b1495af4f1b074ddbfaf0c83d4599e2
Submitter: Jenkins
Branch: master

commit a80c32587b1495af4f1b074ddbfaf0c83d4599e2
Author: jfwood <email address hidden>
Date: Sat Sep 19 17:12:44 2015 -0500

    Add missing X-xxxx HTTP headers to the unauth context

    The unauth context is used by Barbican out of the box for local API evaluation
    as well as for deployments where an authenticating proxy (such as Repose) is
    placed in front of Barbican. Hence this unauth context must provide all the
    required HTTP header settings to the Barbican context prior to policy engine
    computation for RBAC and so forth. This CR provides those missing headers.

    Change-Id: Ib1d6abdb384f5883aa06ec1b6811c3ad80291568
    Closes-Bug: #1497639

Changed in barbican:
status: In Progress → Fix Committed
Thierry Carrez (ttx)
Changed in barbican:
milestone: none → liberty-rc1
status: Fix Committed → Fix Released
Thierry Carrez (ttx)
Changed in barbican:
milestone: liberty-rc1 → 1.0.0
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.