Using an LDIF to Extend NSL Schema

dguest Absent Member.
Absent Member.
0 0 2,959
0 Likes

Problem



A user tried to extend the LDAP Schema on Critical Path Directory Server version 4.2 by running LDAPSchema.Exe that came with SecureLogin v3.5.1 but it didn't work as expected. The reason is that LDAPSchema.Exe should only be run when using the SecureLogin LDAP client with eDirectory or Sun One as the SSO data store. All other LDAP compliant Directory servers, including Critical Path, require an LDIF file.



Solution




  1. With an LDIF file, use ldapmodify instead to extend the schema correctly.

  2. Set up the SSL certificates.

  3. Install the SecureLogin LDAP client.

  4. Assign the appropriate ACL's so SecureLogin will run.



Here is the LDIF file for extending the schema - thanks to David Guest!

The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.