Bug 1041918 - [RFE][keystone]: Handling ACLs that use UserIDs in Federated Keystone
Summary: [RFE][keystone]: Handling ACLs that use UserIDs in Federated Keystone
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: RFEs
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: RHOS Maint
QA Contact:
URL: https://blueprints.launchpad.net/keys...
Whiteboard: upstream_milestone_none upstream_stat...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-12 20:04 UTC by RHOS Integration
Modified: 2015-03-19 17:01 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-03-19 17:01:47 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description RHOS Integration 2013-12-12 20:04:14 UTC
Cloned from launchpad blueprint https://blueprints.launchpad.net/keystone/+spec/acls-userids-federation.

Description:

Temporary user entries created for the same federated user would normally get different user IDs assigned to them  by Keystone. Services that use user-ids in ACL would not normally work correctly in this environment as they would not know the user ID. This blueprint specifies a modification to Keystone that ensures that multiple sequential temporary entries created for the same federated user will get the same user-id assigned to them.

Specification URL (additional information):

https://wiki.openstack.org/wiki/Keystone/Federation/UserIDsInACLs#Handling_ACLs_that_use_UserIDs_in_Federated_Keystone


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