When you set up LDAP-UX, the /etc/opt/ldapux_client.conf file
is automatically created to specify where the directory is, specify
the profile data path, and specify logging configuration. In previous
releases, typically, this file has the following contents:
Service: NSS
LDAP_HOSTPORT="192.1.2.3:389"
PROFILE_ENTRY_DN="cn=caprofile,
CN=Configuration,DC=ab,DC=ny,DC=com"
PROGRAM="/opt/ldapux/config/create_profile_cache"
With the support of ADS multiple domains, this file has been
changed to contain more information. A new keyword "PROFILE_ID"
has been introduced to specify the role of each configuration section.
PROFILE_ID has three possible values:
"local":
specifies the information for the local domain.
Service: NSS
PROFILE_ID="local"
LDAP_HOSTPORT="serverA.ca.com:389"
PROFILE_ENTRY_DN="cn=caprofile,
CN=Configuration,DC=ca,DC=com"
PROGRAM="/opt/ldapux/config/create_profile_cache"
"la.ca.com":
specifies the information for the remote domain.
PROFILE_ID="la.ca.com"
LDAP_HOSTPORT="serverB.la.ca.com:389"
PROFILE_ENTRY_DN="cn=ldapuxprofile,cn=configuration,dc=la,dc=ca,dc=com"
PROGRAM="/opt/ldapux/config/create_profile_cache
-i /etc/opt/ldapux/domain_profiles/ldapux_profile.ldif.la.ca.com
-o /etc/opt/ldapux/domain_profiles/ldapux_profile.bin.la.ca.com"
"gc": specifies
the information for Global Catalog Server.
PROFILE_ID="gc"
LDAP_HOSTPORT="serverA.ca.com:389"
PROFILE_ENTRY_DN="cn=globalprofile,CN=Configuration,DC=la,DC=ca,
DC=com"
PROGRAM="/opt/ldapux/config/create_profile_cache
-i /etc/opt/ldapux/domain_profiles/ldapux_profile.ldif.gc -o /etc/opt/ldapux/domain_profiles/ldapux_profile.bin.gc
The contents of this file are created as you run the setup
tool. Therefore, the sequence in this file represents the sequence
you create remote domains, while running setup, which is also the
sequence that LDAP-UX will connect to domain controllers to perform
the search. The local domain is created first, followed by remote
domains, followed by the global catalog server, then lastly the
domains inside the forest which have not been configured during
remote domain configuration.
If you configure remote domains without using the GCS, the
file will only include information for remote domains. If you skip
remote domains and just configure GCS, the ldapux_client.conf file
will have the "local" section immediately followed by the "gc" section.
Any remote domain sections in the file after the "gc" section are
remote domains in the forest you configure. They are only used by
LDAP-UX to download profiles from the server, and will be ignored
by LDAP-UX for the multiple domain search scope.