use mapping_id for shadow users
Bug #1641639 reported by
Steve Martinelli
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Identity (keystone) |
Fix Released
|
Wishlist
|
Adam Young |
Bug Description
Currently, shadow users are created for users that log in through federation. New "local_user" accounts are created with a new UUID. Rather than creating a new UUID, we should re-use the mapping_id backend that was employed with LDAP users.
Changed in keystone: | |
milestone: | ocata-2 → none |
Changed in keystone: | |
assignee: | nobody → Adam Young (ayoung) |
status: | Confirmed → In Progress |
To post a comment you must log in.
With the existing mapping backend, would it be possible to still get random UUIDs? At that point, is the mapping_id backend a mapping backend anymore? Would it make more sense for it to be just a thing that supplies IDs?