This manual page is for Mac OS X version 10.6.3

If you are running a different version of Mac OS X, view the documentation locally:

  • In Terminal, using the man(1) command

Reading manual pages

Manual pages are intended as a quick reference for people who already understand a technology.

  • For more information about the manual page format, see the manual page for manpages(5).

  • For more information about this technology, look for other documentation in the Apple Reference Library.

  • For general information about writing shell scripts, read Shell Scripting Primer.



SLAPO-TRANSLUCENT(5)                                                                    SLAPO-TRANSLUCENT(5)



NAME
       slapo-translucent - Translucent Proxy overlay to slapd

SYNOPSIS
       /etc/openldap/slapd.conf

DESCRIPTION
       The  Translucent  Proxy  overlay can be used with a backend database such as slapd-bdb(5) to create a
       "translucent proxy".  Entries retrieved from a remote LDAP server may have  some  or  all  attributes
       overridden,  or  new attributes added, by entries in the local database before being presented to the
       client.

       A search operation is first populated with entries from the remote LDAP  server,  the  attributes  of
       which  are  then overridden with any attributes defined in the local database. Local overrides may be
       populated with the add, modify , and modrdn operations, the use of which is restricted  to  the  root
       user.

       A  compare  operation  will perform a comparison with attributes defined in the local database record
       (if any) before any comparison is made with data in the remote database.

CONFIGURATION
       The Translucent Proxy overlay uses a remote LDAP server which is configured with the options shown in
       slapd-ldap(5).   These  slapd.conf  options  are specific to the Translucent Proxy overlay; they must
       appear after the overlay directive.

       translucent_strict
              By default, attempts to delete attributes in either the local  or  remote  databases  will  be
              silently  ignored.  The translucent_strict directive causes these modifications to fail with a
              Constraint Violation.

       translucent_no_glue
              This configuration option disables the automatic creation of "glue" records for an add or mod-rdn modrdn
              rdn  operation,  such that all parents of an entry added to the local database must be created
              by hand. Glue records are always created for a modify operation.

       translucent_local <attr[,attr...]>
              Specify a list of attributes that should be searched for in the local database when used in  a
              search  filter.  By default, search filters are only handled by the remote database. With this
              directive, search filters will be split into a local and remote portion, and local  attributes
              will be searched locally.

       translucent_remote <attr[,attr...]>
              Specify a list of attributes that should be searched for in the remote database when used in a
              search filter. This directive complements the translucent_local directive. Attributes  may  be
              specified as both local and remote if desired.

       If  neither translucent_local nor translucent_remote are specified, the default behavior is to search
       the remote database with the complete search filter. If only translucent_local is specified, searches
       will  only  be run on the local database. Likewise, if only translucent_remote is specified, searches
       will only be run on the remote database. In any case, both the local and remote entries corresponding
       to a search result will be merged before being returned to the client.


CAVEATS
       The  Translucent  Proxy  overlay will disable schema checking in the local database, so that an entry
       consisting of overlay attributes need not adhere to the complete schema.

       Because the translucent overlay does not perform any DN rewrites,   the  local  and  remote  database
       instances must have the same suffix.  Other configurations will probably fail with No Such Object and
       other errors.

FILES
       /etc/openldap/slapd.conf
              default slapd configuration file

SEE ALSO
       slapd.conf(5), slapd-ldap(5).



OpenLDAP 2.4.11                                  2008/07/16                             SLAPO-TRANSLUCENT(5)

Reporting Problems

The way to report a problem with this manual page depends on the type of problem:

Content errors
Report errors in the content of this documentation with the feedback links below.
Bug reports
Report bugs in the functionality of the described tool or API through Bug Reporter.
Formatting problems
Report formatting mistakes in the online version of these pages with the feedback links below.

Did this document help you? Yes It's good, but... Not helpful...