Sun Desktop Manager 1.0 Installation Guide

Appendix B Using OpenLDAP and Active Directory with the Desktop Manager

Using an OpenLDAP Server with the Desktop Manager

To use an OpenLDAP server as the repository for the Desktop Manager data, the schema of the server must be extended to feature the object classes and attributes used to store configuration data. A custom schema file named apoc.schema can be found in the /usr/share/webconsole/apoc/deploy directory.

This file must be copied in the schema subdirectory of the OpenLDAP configuration directory (/etc/openldap) and added to the OpenLDAP schema by including it in the slapd.conf file located in that directory. This is done by inserting a line that reads include /etc/openldap/schema/apoc.schema at the end of the sequence of schema includes that are present in that file. For more information on extending the schema of an OpenLDAP server, refer to the server's manual.

Having extended the OpenLDAP servers schema, the rest of the configuration can be completed using the Add Configuration Repository wizard in the Desktop Manager.

Note –

The Desktop Manager Agent will try and connect to the OpenLDAP server anonymously by providing the DN of the user it requires data for, but no password. This mode of anonymous authentication can be disabled by default in some releases of OpenLDAP servers, in which case it must be enabled by adding a line reading allow bind_anon_cred in the common server parameters defined in the file slapd.conf located in the OpenLDAP configuration directory (/etc/openldap). For more information on that parameter, refer to the server's manual.

Using an Active Directory Server with the Desktop Manager

To use an Active Directory server as a repository for the Desktop Manager data, the schema of the server must be extended to feature the object classes and attributes used to store configuration data. A schema extension file named apoc-ad.ldf can be found in the /usr/share/webconsole/apoc/deploy directory.

The apoc-ad.ldf file must be imported in the Active Directory schema using the following steps:

Enable schema extensions. Refer to Active Directory documentation for more information on how to perform that operation.
Execute the following from the command prompt: ldifde -i -c "DC=Sun,DC=COM" <BaseDN> -f apoc-ad-registry.ldf.

Note –
Replace <BaseDN> with the Active Directory base DN.

Having extended the Active Directory servers schema, the rest of the configuration can be completed using the Add Configuration Repository wizard in the Desktop Manager.

When prompted for LDAP credentials in the Add Configuration Repository wizard, provide the full DN and password of a user with read rights to the tree. This can be a user that is not able to use Active Directory for any other purpose. Refer to Active Directory documentation for more information on how to setup such a user. In addition, the domain name for the Active Directory must be known to the machine that is running the Desktop Manager. You can do this by adding a line mapping the IP address of the Active Directory server with its domain name to the /etc/hosts file of that machine.

In order to retrieve the configuration data from a desktop host, the domain name of the Active Directory must also be known to that host. Authentication of the desktop user can be done in two ways: anonymously and using GSSAPI.

To authenticate using anonymous connections, the Active Directory server must be configured to grant read rights to everyone. Refer to Active Directory documentation for more information on how to perform that operation.
To authenticate using GSSAPI, the user must have authenticated against the Active Directory and the user credentials must be available on the system. This can be achieved by configuring Kerberos authentication on your system, which will generate these credentials when logging in, please refer to the administration guides for your system to find out more information on how to do this.