This section provides the following information to help you configure Data ONTAP to connect to your LDAP database:
The LDAP base is the distinguished name of the LDAP tree in which user information is stored. All lookup requests sent to the LDAP server will be limited to the search base and scope specified by the ldap.base option value, unless further restricted by a more specific base and scope lookup value, such as ldap.base.passwd, ldap.base.group, or ldap.base.passwd.
To specify which LDAP base distinguished name to use for looking up user names, complete the following step.
| 1 |
options ldap.base name name is the base distinguished name. Use quotes around names with embedded spaces. Exampleoptions ldap.base "o=networkappliance,c=us" |
You can, though it is not required, specify base and scope values specifically for LDAP lookup requests, to limit user lookup queries to the user account branch of your LDAP database. Limiting the search base and scope of every query can significantly improve performance.
To specify base and scope values for all LDAP lookup services, complete the following steps.
Note
The values you assign using this procedure will apply to all LDAP lookups, unless you enter separate base and scope values for user-mapping.
Note
Once you specify the search base and scope values for ldap.base.passwd and ldap.base.group, these values take precedence over the search base and scope set for ldap.base, for password and group lookups.
To specify the LDAP servers to be used for LDAP queries, complete the following step.
You might want to specify LDAP servers that are on faster links as the preferred servers.
To specify the LDAP servers that you want the storage system to attempt to connect to first, complete the following step.
To enable or disable LDAP on your storage system, complete the following step.
| 1 |
options ldap.enable {on | off}
|
To enable or disable secure sockets layer (SSL) encrypting of LDAP traffic on your storage system, complete the following step.
| 1 |
options ldap.ssl.enable {on | off}
|
In addition to enabling SSL for LDAP, you must have a root authority-signed certificate installed on your storage system. For more information see Installing a root certificate for SSL for LDAP traffic.
Note
The same certificate-signing authority must issue both the certificate on the storage system and the certificate on the server.
To install a root certificate for use for secure sockets layer (SSL) encrypting of LDAP traffic on your storage system, complete the following steps.
| 1 |
Download a certificate from your preferred trusted signing authority to the storage system. Remember the certificate's location on the storage system. |
| 2 |
keymgr install root certificate_filename certificate_filename is the complete file name for the certificate. After the keymgr command installs the certificate, you can remove the copy you placed on the storage system. Examplekeymgr install root /etc/my_cert |
| 3 |
Set the LDAP port to port 636. For information on setting the LDAP port, see Specifying the LDAP port |
Note
The same certificate-signing authority must issue both the certificate on the storage system and the certificate on the server.
To edit the /etc/nsswitch.conf file for LDAP, complete the following steps.
If anonymous authentication does not work in your environment, you need to specify an administrative user name.
To specify the user name to be used for administrative queries for looking up UIDs and GIDs, complete the following step.
To specify a password for the administrative user, complete the following step.
| 1 |
options ldap.passwd password password is the password for the administrative user. The password is displayed as a series of asterisks. |
You might need to specify the port to use for LDAP queries if the LDAP server has been set up to use a port other than the default for LDAP, port 389.
To specify the LDAP port, complete the following step.
| 1 |
options ldap.port N |
Data ONTAP chooses an LDAP server based on your LDAP server option settings, as described in the following table.
.|
When specified, servers listed in this option value will be tried first, according to list order. | |
ldap.servers |
When no ldap.preferred.servers are specified, or specified servers are not available, servers designated in this option value will be tried, according to list order. |
|
When no ldap.preferred.servers and no ldap.servers are specified or available, servers designated in this option value will be tried using domain controller selection methodology. For information about domain controller selection methodology, see Monitoring CIFS activity. |
Copyright © 1994-2005, Network Appliance, Inc. All rights
reserved.
Part No. 210-01086_B0
File: 7multi22.htm
Last updated: 08-Dec-2005 13:19:49