8943e57ee6
This patch fixes some issues with LDAP client configuration on ONTAP SVMs. With ldap security service, users should be able to configure a LDAP client that can be used for authentication and name mapping. The name service switch order remains: ldap,files. Issues fixed: - The driver now identifies when user provide a Active Directory domain or a Linux/Unix LDAP server IP and sets the correct schema. - LDAP configuration parameter `servers` was replaced by `ldap-servers` in ONTAP 9.2, and now accepts host names too. - Fix DNS configuration for LDAP security service - User can now specify base search DN for LDAP queries, which can be mandatory for Unix/Linux servers, using the security service `ou` parameter. Closes-Bug: #1916534 Change-Id: Ieaa53abbe50e7b708e508c132dfc4bb36b71a4f5 Signed-off-by: Douglas Viroel <viroel@gmail.com>
18 lines
994 B
YAML
18 lines
994 B
YAML
---
|
|
fixes:
|
|
- |
|
|
NetApp ONTAP driver is now fixed to properly configure SVM LDAP client when
|
|
configuration is provided through `ldap` security service. Now, the driver
|
|
chooses the correct LDAP schema based on the given security service
|
|
parameters. The `RFC-2307` schema will be set for Linux/Unix LDAP servers
|
|
and `RFC-2307bis` for Active Directory servers. When using a Linux/Unix
|
|
LDAP server, the security service should be configured setting the
|
|
`server` parameter with servers IPs or host names. For Active
|
|
Directory LDAP server, the domain information must be configured using the
|
|
the `domain` parameter. Users should provide at least one DNS server when
|
|
configuring servers by its host or domain names. The base search
|
|
`distinguished name` used for LDAP queries can now be configured using
|
|
security service `ou` parameter. Please refer to
|
|
`Launchpad Bug #1916534 <https://bugs.launchpad.net/manila/+bug/1916534>`_
|
|
for more details.
|