Although directory servers typically ship with support for a wide range of standard schema, most LDAP-enabled applications of any significance will require custom schema elements for use in representing the data for that application. All servers provide some mechanism for updating the schema defined in that server, but there is not necessarily a standard way to accomplish this. However, the long-expired draft-poitou-ldap-schema-update-02 Internet Draft does propose an approach that a number of servers support. This draft states that new schema elements should be added by performing a modify operation against the subschema subentry using the add modification type to specify the desired changes.
For example, the following demonstrates the process that could be used to add two new attribute types, example-test-attr-1 and example-test-attr-2, and an auxiliary object class, example-test-oc. It assumes that we have already determined that the appropriate schema is defined in the “cn=schema” entry:
dn: cn=schema changetype: modify add: attributeTypes attributeTypes: ( 18.104.22.168.4.1.32422.214.171.124 NAME 'example-test-attr-1' DESC 'A first example attribute' EQUALITY caseIgnoreMatch ORDERING caseIgnoreOrderingMatch SUBSTR caseIgnoreSubstringsMatch SYNTAX 126.96.36.199.4.1.14188.8.131.52.15 ) attributeTypes: ( 184.108.40.206.4.1.324220.127.116.11 NAME 'example-test-attr-2' DESC 'A second example attribute' EQUALITY caseIgnoreMatch ORDERING caseIgnoreOrderingMatch SUBSTR caseIgnoreSubstringsMatch SYNTAX 18.104.22.168.4.1.1422.214.171.124.15 ) - add: objectClasses objectClasses: ( 126.96.36.199.4.1.324188.8.131.52 NAME 'example-test-oc' SUP top AUXILIARY MAY ( example-test-attr-1 $ example-test-attr-2 ) ) -
Removing a schema element may be possible using the delete modification type to remove the specific values that correspond to the schema elements that are no longer desired. However, this is more problematic than adding new schema elements for several reasons. First, if any data in the server makes use of a given schema element, then some ways of interacting with that data could be adversely affected by removing that element. In addition, there may be problems with removing a schema element that may be extended by another schema element (e.g., removing an object class from which another class inherits). In general, removing a schema element is discouraged without first making sure that the element is not referenced by any data, configuration, or schema.
Replacing an existing schema element may be possible by performing a modification that combines the removal of the old value and the addition of the new value. The changes should be made in the same modify operation so that they will be processed atomically and there will not be any intermediate period of time in which the former element is removed and the new element is not yet added.
It is possible that some servers may offer alternate approaches for managing the schema. Consult the documentation for the directory server you are using to determine the best way to manage the schema for that server.