How do I configure an LDAP Version 3 data store to point to a newly installed Sun Java System Directory Server instance?
The procedure below assumes that you have installed Directory Server with the default sample data and the example organization directory information tree (DIT). You can select both options during installation. It is also assumed that you did not install Access Manager on Directory Server. Out of the box, Access Manager defines a set of object classes and attributes that are required in Directory Server for its management on Access Manager. Alternatively, you can modify Access Manager’s object classes and attributes to match those in Directory Server. In the Access Manager Administration Console, you can manage users based on Access Manager’s predefined object classes and attributes as specified in the XML files. If Directory Server does not have the necessary object classes or attributes defined, then any access that involves the missing classes or attributes will fail. For example, when you create a user on the Administration Console, the Administration Console writes to Directory Ser
Related Questions
- Does Skelta Workflow.NET 2004 have the ability to integrate with / pull data from (SUN) LDAP directory for user data - i.e., allow for custom implementation of a user data source?
- How do I configure an LDAP Version 3 data store to point to Directory Server with the Access Manager schema installed?
- How do I configure an LDAP Version 3 data store to point to a newly installed Active Directory Server instance?
