openstack
/
keystone-specs
Code Issues Proposed changes

Repropose federated attributes in the user API for Train 

Most of the work for this has already been done, and with the move
towards predictable IDs, there is a real need for a mechanism
to prepopulate the users as part of the synchronization process.

https://review.openstack.org/#/c/612099/

Related-Bug: 1816076

Change-Id: I9906a9d76479364134ef21a0cf578ff6d5cf07b9
This commit is contained in:
Kristi Nikolla 2019-04-17 13:02:47 -04:00
parent 22af4130de
commit 9ecdbc9802
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
specs/keystone/backlog/support-federated-attr.rst → specs/keystone/train/support-federated-attr.rst
View File

@ -145,7 +145,7 @@ like any other Keystone user.
Alternatives
------------
Continue with shadow mapping [2] as the only option for providing federated
Continue with shadow mapping [3] as the only option for providing federated
user provisioning.
We could extend OS-FEDERATION to support federated user operations.
@ -188,11 +188,11 @@ Assignee(s)
Primary assignee:
- Ron De Rose
- Kristi Nikolla
Other contributors:
- TBD
- Ron De Rose
Work Items
----------