Translations:ReleaseNotes/Kilo/65/en


 * Filter parameters specified by API users are now processed by LDAP itself, instead of by Keystone.
 * Experimental support was added to store domain-specific identity backend configuration in SQL using the HTTP API. The primary use case for this is to create a new domain with the HTTP API, and then immediately configure a domain-specific LDAP driver for it without restarting Keystone.