In response to comment #10. Keystone has merged a spec that will allow deployers to define more descriptive mappings [0]. This should mitigate #1 from comment #10.
Since using a direct role assignment works around this bug, we can track the progress of the mapping engine with the blueprint [1].
In response to comment #10. Keystone has merged a spec that will allow deployers to define more descriptive mappings [0]. This should mitigate #1 from comment #10.
Since using a direct role assignment works around this bug, we can track the progress of the mapping engine with the blueprint [1].
[0] http:// specs.openstack .org/openstack/ keystone- specs/specs/ keystone/ ocata/shadow- mapping. html /blueprints. launchpad. net/keystone/ +spec/shadow- mapping
[1] https:/