← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1804523] Re: Federated protocol API doesn't use default roles

 

Reviewed:  https://review.openstack.org/625354
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=87d93db90950065410e8fcb2866effc96c7153e4
Submitter: Zuul
Branch:    master

commit 87d93db90950065410e8fcb2866effc96c7153e4
Author: Lance Bragstad <lbragstad@xxxxxxxxx>
Date:   Fri Dec 14 21:13:35 2018 +0000

    Implement system admin role in protocol API
    
    This commit introduces the system admin role to the protocol API,
    making it consistent with other system-admin policy definitions.
    
    Subsequent patches will build on this work to expose more
    functionality to domain and project users:
    
     - domain user test coverage
     - project user test coverage
    
    Change-Id: I9384e0fdd95545f1afef65a5e97e8513b709f150
    Closes-Bug: 1804523
    Related-Bug: 1806762


** Changed in: keystone
       Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Identity (keystone).
https://bugs.launchpad.net/bugs/1804523

Title:
  Federated protocol API doesn't use default roles

Status in OpenStack Identity (keystone):
  Fix Released

Bug description:
  In Rocky, keystone implemented support to ensure at least three
  default roles were available [0]. The protocol (federation) API
  doesn't incorporate these defaults into its default policies [1], but
  it should.

  [0] http://specs.openstack.org/openstack/keystone-specs/specs/keystone/rocky/define-default-roles.html
  [1] https://git.openstack.org/cgit/openstack/keystone/tree/keystone/common/policies/protocol.py?id=fb73912d87b61c419a86c0a9415ebdcf1e186927

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1804523/+subscriptions


References