Table of Contents

Search

  1. Preface
  2. Introduction to PowerExchange
  3. DBMOVER Configuration File
  4. Netport Jobs
  5. PowerExchange Message Logs and Destination Overrides
  6. SMF Statistics Logging and Reporting
  7. PowerExchange Security
  8. Secure Sockets Layer Support
  9. PowerExchange Alternative Network Security
  10. PowerExchange Nonrelational SQL
  11. PowerExchange Globalization
  12. Using the PowerExchange ODBC Drivers
  13. PowerExchange Datatypes and Conversion Matrix
  14. DTL__CAPXTIMESTAMP Time Stamps
  15. PowerExchange Glossary

Example: LDAP Configuration with a Filter and Login Attribute

Example: LDAP Configuration with a Filter and Login Attribute

The following example shows the DBMOVER statements for an LDAP configuration that defines a filter and login attribute:
SECURITY=(1,N,LDAP) LDAP_HOST=(myldapserver,389) LDAP_BIND_DN="uid=hmiller,ou=People,dc=example,dc=com" LDAP_BIND_EPWD=47D95F9932FB5F67 LDAP_BASE=("ou=People,dc=example,dc=com")
LDAP_FILTER="(objectclass=person)" LDAP_LOGIN_ATTRIBUTE=cn
This filter restricts the LDAP search to LDAP entries with an
objectclass
attribute that matches the value
person
.
Filtering can speed up searches because LDAP indexes can be used to reduce the number of searched entries. Without the LDAP_FILTER statement, the default filter of
(objectclass=*)
is used, which would match entries that have any
objectclass
value.
The login attribute of
cn
directs the search for an LDAP entry that has a common name that matches the PowerExchange user identity.
In an actual application, because common name is not unique, you would not use it as a login key.
The LDAP_BIND_EPWD statement specifies an encrypted password for the search user.