1SLAPO-TRANSLUCENT(5)          File Formats Manual         SLAPO-TRANSLUCENT(5)
2
3
4

NAME

6       slapo-translucent - Translucent Proxy overlay
7

SYNOPSIS

9       /etc/openldap/slapd.conf
10

DESCRIPTION

12       The  Translucent Proxy overlay can be used with a backend database such
13       as slapd-bdb(5) to create a  "translucent  proxy".   Entries  retrieved
14       from  a  remote LDAP server may have some or all attributes overridden,
15       or new attributes added, by entries in the local database before  being
16       presented to the client.
17
18       A search operation is first populated with entries from the remote LDAP
19       server, the attributes of which are then overridden with any attributes
20       defined  in  the  local database. Local overrides may be populated with
21       the add, modify , and modrdn operations, the use of which is restricted
22       to the root user.
23
24       A  compare  operation will perform a comparison with attributes defined
25       in the local database record (if any) before  any  comparison  is  made
26       with data in the remote database.
27

CONFIGURATION

29       The  Translucent  Proxy overlay uses a remote LDAP server which is con‐
30       figured with the options  shown  in  slapd-ldap(5).   These  slapd.conf
31       options  are specific to the Translucent Proxy overlay; they may appear
32       anywhere after the overlay directive and before any subsequent database
33       directive.
34
35       translucent_strict
36              By default, attempts to delete attributes in either the local or
37              remote  databases  will  be  silently  ignored.   The   translu‐
38              cent_strict  directive causes these modifications to fail with a
39              Constraint Violation.
40
41       translucent_no_glue
42              This configuration option disables  the  automatic  creation  of
43              "glue"  records  for  an  add or modrdn operation, such that all
44              parents of an entry added to the local database must be  created
45              by hand. Glue records are always created for a modify operation.
46

CAVEATS

48       The Translucent Proxy overlay will disable schema checking in the local
49       database, so that an entry consisting of overlay  attributes  need  not
50       adhere to the complete schema.
51
52       Because  the translucent overlay does not perform any DN rewrites,  the
53       local and remote database instances must have the same  suffix.   Other
54       configurations will probably fail with No Such Object and other errors.
55

FILES

57       /etc/openldap/slapd.conf
58              default slapd configuration file
59

SEE ALSO

61       slapd.conf(5), slapd-ldap(5).
62
63
64
65OpenLDAP 2.3.34                    2007/2/16              SLAPO-TRANSLUCENT(5)
Impressum