Default PingDirectory server schema files
The PingDirectory server stores its schema as a set of LDIF files for the server instance in the <server-root>/config/schema
directory. The PingDirectory server reads the schema files in alphanumeric order at startup in the following order:
-
The
00-core.ldif
file -
The
01-pwpolicy.ldif
file -
Remaining files
You should name custom schema files so that they are loaded in last. For example, custom schema elements could be saved in a file labeled 99-user.ldif
that loads after the default schema files are read at startup.
The PingDirectory server then uses the schema definitions to determine any violations that might occur during add
, modify
, or import
requests. Clients applications check the schema (matching rule definitions) to determine the assertion value algorithm used in comparison or search operations.
The default set of schema files are present at installation and should not be modified. Modifying the default schema files could result in an inoperable server.
The schema files have the following descriptions.
Schema Files | Description |
---|---|
|
Governs the PingDirectory server’s core functions |
|
Governs password policies |
|
Governs the PingDirectory server’s configuration |
|
Governs the PingDirectory server’s change log |
|
Governs Java objects |
|
Governs Common Object Request Broker Architecture (CORBA) object references |
|
Governs calendar attributes for vCard |
|
Governs Server Location Protocol (SLP) mappings to and from LDAP schemas |
|
Governs PKCS #9 public-key cryptography |
|
Governs LDAP authentication passwords |
|
Governs printer services |
|
Governs web services registries of Service Oriented Architecture (SOA) components |
|
Governs mapping entities from TCP/IP and UNIX into X.500 entries |