Bug 1189633 - [RFE][keystone]: Scope federated token with 'token' identity method
Summary: [RFE][keystone]: Scope federated token with 'token' identity method
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-keystone
Version: unspecified
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: Upstream M2
: 7.0 (Kilo)
Assignee: Nathan Kinder
QA Contact: yeylon@redhat.com
URL: https://blueprints.launchpad.net/keys...
Whiteboard: upstream_milestone_kilo-2 upstream_de...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-02-05 14:17 UTC by RHOS Integration
Modified: 2016-04-26 20:11 UTC (History)
6 users (show)

Fixed In Version: openstack-keystone-2015.1.0-1.el7ost
Doc Type: Enhancement
Doc Text:
The Identity service now allows unscoped federation tokens to be used to obtain a scoped token using the 'token' authentication method. When using the Identity service's federation extension, an unscoped federation token is returned as a result of the initial authentication. This is then exchanged for a scoped token. An unscoped federation token previously had to use the 'saml2' or 'mapped' authentication to obtain a scoped token. This is inconsistent with the method used to exchanging a regular unscoped token for a scoped token, which uses the 'token' method. Exchanging an unscoped federation token for a scoped token now uses the 'token' authentication method, which is consistent with the regular unscoped token behavior.
Clone Of:
Environment:
Last Closed: 2015-08-05 13:20:21 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2015:1548 0 normal SHIPPED_LIVE Red Hat Enterprise Linux OpenStack Platform Enhancement Advisory 2015-08-05 17:07:06 UTC

Comment 8 errata-xmlrpc 2015-08-05 13:20:21 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2015:1548


Note You need to log in before you can comment on or make changes to this bug.