Migrating NIS+ to LDAP

Extending Publickey or Automount Schema Into Netscape Directory ServerExtending Publickey or Automount Schema Into Netscape Directory Server

You must extend your Netscape Directory Server with the publickey schema or new automount schema if you want to migrate the public keys of users and hosts or AutoFS maps from the NIS+ server to your LDAP directory server.

A publickey schema, which is based on IETF RFC 2307-bis is required to migrate the publickeys in the NIS+credential table entries from the NIS+ server to the LDAP directory. A new automount schema, which is based on IETF RFC 2307-bis is required to migrate the AutoFS maps (such as auto_master, auto_home, auto_direct, etc...) from the NIS+ server to the LDAP directory. You need to run the setup program on a LDAP-UX client system, the setup program extends the publickey schema or new automount schema into the LDAP directory.

LDAP-UX does not support the obsolete automount schema which is shipped with Netscape Directory Server 6.x. You must manually delete it before you can succeed to extend the new automount schema into the LDAP directory server.

Use the following steps to extend the publickey schema or the new automount schema into your Netscape Directory Server:

Step 1. Login to your Netscape Directory Server as root.

Step 2. Check the /var/opt/netscape/servers/slapd-<serverID>/config/schema/10r fc2307.ldif file on your Netscape Directory Server to see whether the following two entries exist or not. Look for entries that contains the following fields:

•NAME ’automountInformation’

•NAME ’automount’

The data in these two entries defines the obsolete automount schema. The complete attribute entries are:

•attributeTypes:( 1.3.6.1.1.1.1.25 NAME ’automountInformation’ DESC ’Standard LDAP attribute type’ SYNTAX 1.3.6.1.4.1.1466.115.121.1.26 X-ORIGIN ’RFC 2307’)

Chapter 2

23