My understanding is that -d dumps _from_ LDAP to a localfile format. I want exactly the reverse... I want to take local files and dump them in LDIF format.
Right now, the means by which to do this is to use the PADL migration tools "offline" scripts. For example, if I wanted to setup OpenLDAP for Solaris auth I'd do the following: 1) Setup OpenLDAP, add appropriate schemas. (Getting all the schema's added is a confusing thing, in any LDAP server) 2) Create a base schema (dn=mydomain,dn=com) 3) Use PADL Migration tools (offline) to dump local databases (passwd/group/etc) to LDIF 4) Trim LDIF to taste, remove unwanted system users, groups, etc. 5) ldapadd LDIF to directory server 6) Add DUA junk. (Which seems pointless.) The whole process is nasty. Using Sun DSEE only makes it more complex. OpenDS has simplified life significantly, as steps 1/2 are done during install and significantly less convoluted than DSEE. While I appreciate the work from the PADL guys, Sun is the world leader in LDAP solutions... why are we forced to use 3rd party tools to get auth working in a Solaris environment? ldapaddent starts to solve the problem, but moves the trimming process from the LDIF prior to add to editing the directory itself after add. So, in essence, I want a single tool (ldapaddent) that totally replaces PADL MigrationTools. benr. -- This message posted from opensolaris.org
