This section shows how to configure the OpenLDAP server.
Parameter | Description |
---|---|
suffix | This parameter is the base DN for any searches. Searches such as those set this parameter to the base suffix specified in Table 3. In our example, it is o=yourOrg. |
rootdn | This parameter is the DN of the LDAP "root" user. Although it can have any hierarchy, it can most easily be placed under the suffix. In our example, it is cn=Manager,o=yourOrg. |
rootpw | This parameter is set to a shielded (not encrypted) password at the next step. |
#suffix “dc=my-domain,dc=com” suffix “o=yourOrg” #rootdn “cn=Manager,dc=my-domain,dc=com” rootdn “cn=Manager,o=yourOrg” # # Cleartext passwords, especially for the rootdn, should # be avoided. See slappasswd(8) and slapd.conf(5) for details. # Use of strong authentication encouraged. # rootpw secret
# export SLAPPW=`slappasswd`
# echo "rootpw $SLAPPW" >>slapd.confThe basic configuration of your LDAP server is complete and you are ready to start your LDAP server.
# service ldap startYou should receive a green OK. If not, check for error messages in the /var/log/messages file that relate to the slapd and then run the command again.
# chkconfig --level 235 ldap on
# ldapsearch -h localhost -x -b <base_suffix> ‘(object class=*)’No entries should be returned, though you can expect a positive response from the LDAP server:
# ldapsearch -h localhost -x -b o=yourOrg ‘(objectclass=*)’ version: 2 # filter: (objectclass=*) # requesting: ALL # search result search: 2 result: 32 No such object # numResponses: 1#
If the LDAP server responded correctly to the query, you are ready to configure your LDAP server to work with SAN File System.
Parent topic: Configuring LDAP using OpenLDAP
Previous topic: Configure the OpenLDAP client
Next topic: Configure OpenLDAP with SAN File System