Only the user who create the bay can create and get certificate

Bug #1536883 reported by Hua Wang
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Magnum
Fix Released
Undecided
Hua Wang

Bug Description

Only the user who create the bay can create and get certificate from magnum.

Hua Wang (humble00)
Changed in magnum:
assignee: nobody → Hua Wang (humble00)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to magnum (master)

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

Changed in magnum:
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote :

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

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on magnum (master)

Change abandoned by Hua Wang (<email address hidden>) on branch: master
Review: https://review.openstack.org/274527

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

Reviewed: https://review.openstack.org/285136
Committed: https://git.openstack.org/cgit/openstack/magnum/commit/?id=ce5b55dd31a72a65d9fc3b37576a980b4ed73638
Submitter: Jenkins
Branch: master

commit ce5b55dd31a72a65d9fc3b37576a980b4ed73638
Author: Hua Wang <email address hidden>
Date: Thu Feb 25 18:48:03 2016 +0800

    limit access to certificate and container:create

    Only the user who creates the bay can get the certificate and call
    the certificate signing request of the bay and create containers
    in the bay, which is needed by [1].

    [1] https://github.com/openstack/magnum/blob/master/specs/
        create-trustee-user-for-each-bay.rst

    Change-Id: Id959b76cb136ffbb0e6bcb8c3b83e02b30de66cf
    Closes-Bug: #1536883
    Partially-Implements: blueprint create-trustee-user-for-each-bay

Changed in magnum:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/magnum 2.0.0

This issue was fixed in the openstack/magnum 2.0.0 release.

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.