Bug 1041897 - [RFE][keystone]: Do not check for user when creating assignment
Summary: [RFE][keystone]: Do not check for user when creating assignment
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-keystone
Version: unspecified
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: Upstream M3
: 5.0 (RHEL 7)
Assignee: RHOS Maint
QA Contact: Udi Kalifon
URL: https://blueprints.launchpad.net/keys...
Whiteboard: upstream_milestone_icehouse-3 upstrea...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-12 19:57 UTC by RHOS Integration
Modified: 2016-04-27 00:59 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-06-26 15:26:58 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description RHOS Integration 2013-12-12 19:57:30 UTC 
Cloned from launchpad blueprint https://blueprints.launchpad.net/keystone/+spec/no-check-id.

Description:

Creating an assignment may happen in the absence of User data.  For Federation, a user listing may not even be possible.  Even in LDAP and SQL cases, an admin may need to create role assignments prior to a valid user object being available.  Same is tru for groups. These checks are unnecessary, and can and should be removed.

Specification URL (additional information):

None
Comment 2 Udi Kalifon 2014-03-31 06:41:41 UTC 
This will not be fixed and the RFE is invalid. See my upstream bug on this which was tagged as "invalid":
https://bugs.launchpad.net/keystone/+bug/1298478

Should we close this bz?
Comment 3 Adam Young 2014-04-02 13:23:32 UTC 
Yes, lets close it.  I'll mention to upstream we should remove this line from the release notes, as the BP is not fully implemented.
Note You need to log in before you can comment on or make changes to this bug.