Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1189645

Summary: [RFE][keystone]: Allow for mapping to existing user in federated workflow
Product: Red Hat OpenStack Reporter: RHOS Integration <rhos-integ>
Component: openstack-keystoneAssignee: Nathan Kinder <nkinder>
Status: CLOSED DUPLICATE QA Contact: Mike Abrams <mabrams>
Severity: high Docs Contact:
Priority: high    
Version: unspecifiedCC: ayoung, markmc, nbarcet, yeylon
Target Milestone: Upstream M3Keywords: FutureFeature
Target Release: 7.0 (Kilo)   
Hardware: Unspecified   
OS: Unspecified   
URL: https://blueprints.launchpad.net/keystone/+spec/federated-direct-user-mapping
Whiteboard: upstream_milestone_kilo-3 upstream_definition_approved upstream_status_implemented
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-03-18 18:40:02 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description RHOS Integration 2015-02-05 14:19:30 UTC
Cloned from launchpad blueprint https://blueprints.launchpad.net/keystone/+spec/federated-direct-user-mapping.

Description:

Allow for specifying mapping rules where effective user must exist in the backend. Otherwise map users to default domain named federated.

Specification URL (additional information):

None