JSON Based configuration file for LDAP bindings
LDAP configuration is headed toward its own Domain specific language. Each release brings more options and complexity. The init file format it starting to impede the solutions for things like attribute mapping.
We will extract the LDAP configuration into its own file /etc/keystone/
This might tie in with the AttributeMapping blueprint.
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- Adam Young
- Direction:
- Needs approval
- Assignee:
- Adam Young
- Definition:
- Obsolete
- Series goal:
- None
- Implementation:
- Unknown
- Milestone target:
- None
- Started by
- Completed by
- Dolph Mathews
Related branches
Related bugs
Sprints
Whiteboard
Hi Adam, I adding the etherpad link here which we somewhat discussed in today's IRC Keystone meeting for reference. I hope that makes sense.
https:/
It is critical that this file contain comments so people can understand the options. I have been told json files do not permit comments. Is this true? If so json is a problematic choice for this. Also Im concerned we may end up splitting needed ldap config into two files, this and attribute mapping. Would be helpful to have it all in one place.