Despite the awesomely advanced management interface to Sun DSEE 6.0, I have found that the handy /usr/lib/ldap/idsconfig command that actually initializes the directory with the correct OUs, searchServiceDescriptors, and profiles that the Solaris ldapclient command uses to initialize the OS to use LDAP as a naming service. Also, the idsconfig command is no longer even mentioned in the DSEE 6.0 installation guide nor the administration guide (the logical place to describe this very helpful tool).
So, through a bit more of digging I happened to come across the command and a description of how to modify it to work with DSEE 6.0 in the Sun Java System Identity Synchronization for Windows 6.0 Deployment Planning Guide in Appendix A. (Pluggable Authentication Modules), of all places! Anyway, here an excerpt from that guide that will get you on your way with the idsconfig command:
So, through a bit more of digging I happened to come across the command and a description of how to modify it to work with DSEE 6.0 in the Sun Java System Identity Synchronization for Windows 6.0 Deployment Planning Guide in Appendix A. (Pluggable Authentication Modules), of all places! Anyway, here an excerpt from that guide that will get you on your way with the idsconfig command:
For PAM to work with Directory Server 6.0, you must edit the /usr/lib/ldap/idsconfig script and change 5 to 6 in the following code:
if [ "${IDS_MAJVER}" != "5" ]; then
While executing the idsconfig command-line tool, you need to know which values to assign to the various configuration parameters. If you do not know, use the default values when prompted (other than the configuration parameters 1, 2, and 4).
Finally, I was able to initialize the directory as I was able to with previous versions of the Sun Directory Server. Especially helpful are the profiles that the idsconfig command creates in the directory under cn=profilename,ou=profiles,dc=yourdomain,dc=net which allows the LDAP clients to simply download the profile with all of the configuration options preset and simply copy them locally to become initialized. This saves a lot of time when converting a bunch of systems from file or nis for naming services in the nsswitch.conf file.
For a complete how-to of initializing the Sun Directory Server, please reference my wiki page: http://www.amcpu.org/wiki/index.php?title=SJSDS_Installation_Guide.
Also, for a walkthrough of configuring Solaris LDAP clients, check out this wiki entry: http://www.amcpu.org/wiki/index.php?title=SJSDS_Configure_LDAP_Clients.
For a complete how-to of initializing the Sun Directory Server, please reference my wiki page: http://www.amcpu.org/wiki/index.php?title=SJSDS_Installation_Guide.
Also, for a walkthrough of configuring Solaris LDAP clients, check out this wiki entry: http://www.amcpu.org/wiki/index.php?title=SJSDS_Configure_LDAP_Clients.