The Directory Proxy Server inherits user-defined schema from all external
servers by comparing cn=schema
on these servers at Directory Proxy Server startup and at five minute intervals. As a result,
example.com schema does not need to be added manually to the Directory Proxy Server’s
config/schema directory. We assume that the schema for Sample entries
has been defined on the external servers with the example.com DIT, requiring no direct schema
management on the Directory Proxy Server. The following schema definitions
are assumed to exist on the external Directory Server:
dn: cn=schema objectClass: top objectClass: ldapSubentry objectClass: subschema cn: schema attributeTypes: ( 1.3.6.1.4.1.32473.2.1.1 NAME 'exAccountNumber' SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 SINGLE-VALUE ) attributeTypes: ( 1.3.6.1.4.1.32473.1.1.3 NAME 'sampleLinkedAccounts' SYNTAX 1.3.6.1.4.1.1466.115.121.1.12 ) attributeTypes: ( 1.3.6.1.4.1.32473.1.1.2 NAME 'sampleRegion' SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 SINGLE-VALUE ) attributeTypes: ( 1.3.6.1.4.1.32473.1.1.1 NAME 'sampleID' SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 SINGLE-VALUE ) attributeTypes: ( 1.3.6.1.4.1.32473.2.1.3 NAME 'exSampleLinkedAccounts' SYNTAX 1.3.6.1.4.1.1466.115.121.1.12 ) attributeTypes: ( 1.3.6.1.4.1.32473.2.1.2 NAME 'exSampleRegion' SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 SINGLE-VALUE ) objectClasses: ( 1.3.6.1.4.1.32473.2.2.1 NAME 'exampleAccount' SUP top AUXILIARY MAY ( exAccountNumber $ exSampleRegion $ exSampleLinkedAccounts $ sampleID $ sampleRegion $ sampleLinkedAccounts ) )
The schema file defines some Example.com schema, such as exAccountNumber
and
exSampleRegion
, and some Sample schema, such as
sampleRegion
and sampleID
.