Go to main content

Working With Oracle® Solaris 11.4 Directory and Naming Services: LDAP

Exit Print View

Updated: November 2020
 
 

Setting Up the NIS-to-LDAP Service

You can use the standard mappings or custom mappings to set up the N2L service, as described in the procedures in this section.

As part of the NIS-to -LDAP conversion, you need to run the inityp2l command. This command runs an interactive script for which you must provide configuration information. For more information about the types of information you need to provide for configuration, see the ypserv(8) man page. This information typically includes:

  • The name of the configuration file being created. The default configuration file is /etc/default/ypserv.

  • The DN that stores configuration information in LDAP. The default value is ypserv.

  • Preferred server list for mapping data to LDAP.

  • Preferred server list for mapping data from LDAP.

  • Authentication method for mapping data to LDAP.

  • Authentication method for mapping data from LDAP.

  • TLS method for mapping data to LDAP.

  • TLS method for mapping data from LDAP.

  • Proxy user bind DN to read or write data from LDAP.

  • Proxy user bind DN to read or write data to LDAP.

  • Proxy user password to read or write data from LDAP.

  • Proxy user password to read or write data to LDAP.

  • Timeout value (in seconds) for an LDAP bind operation.

  • Timeout value (in seconds) for an LDAP search operation.

  • Timeout value (in seconds) for an LDAP modify operation.

  • Timeout value (in seconds) for an LDAP add operation.

  • Timeout value (in seconds) for an LDAP delete operation.

  • Time limit (in seconds) for search operation on the LDAP server.

  • Size limit (in bytes) for search operation on the LDAP server.

  • Whether N2L should follow LDAP referrals.

  • LDAP retrieval error action, number of retrieval attempts, and timeout (in seconds) between each attempt.

  • Store error action, number of attempts, and timeout (in seconds) between each attempt.

  • Mapping file name.

  • Whether to generate mapping information for auto_direct map.

    The script places relevant information regarding custom maps at appropriate places in the mapping file.

  • The naming context.

  • Whether to enable password changes.

  • Whether to change the default TTL values for any map.


Note -  Many LDAP servers do not support sasl/cram-md5 authentication.