Add configuration for different backend identity types
Registered by
Gabriel Hurley
Until Keystone has a means of querying the backend identity system (LDAP, keystone's built-in user/project system, etc) which is being used, Horizon should add a setting to configure the identity backend so that we can control behavior such as whether or not users/projects can be updated, users can change their own passwords, etc.
This may require more than simply setting the "type" of backed (e.g. LDAP) but instead having a dict-config-style set of capabilities for the backend (e.g. {"can_add_users": True, ...}).
Blueprint information
- Status:
- Complete
- Approver:
- Devin Carlen
- Priority:
- Medium
- Drafter:
- Gabriel Hurley
- Direction:
- Approved
- Assignee:
- Registry Administrators
- Definition:
- Approved
- Series goal:
- Accepted for essex
- Implementation:
- Implemented
- Milestone target:
- None
- Started by
- Gabriel Hurley
- Completed by
- Gabriel Hurley
Related branches
Related bugs
Sprints
Whiteboard
This was actually implemented back in Essex... https:/
(?)