directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gerald Turner (JIRA)" <>
Subject [jira] [Created] (DIRAPI-154) Implement "online" OpenLDAP schema parsing in DefaultSchemaLoader
Date Wed, 21 Aug 2013 18:23:53 GMT
Gerald Turner created DIRAPI-154:

             Summary: Implement "online" OpenLDAP schema parsing in DefaultSchemaLoader
                 Key: DIRAPI-154
             Project: Directory Client API
          Issue Type: Improvement
    Affects Versions: 1.0.0-M20
            Reporter: Gerald Turner

The constructor in DefaultSchemaLoader has the following comment:
  // TODO Handle schema loading on other LDAP servers

For OpenLDAP this would require searching subtree under cn=schema,cn=config and handling attributes

  olcAttributeTypes: {1}( NAME ( 'sn' 'surname' ) DESC 'RFC2256: last (family) name(s)
for which the entity is known by' SUP name )

  olcObjectClasses: {4}( NAME 'person' DESC 'RFC2256: a person' SUP top STRUCTURAL
MUST ( sn $ cn ) MAY ( userPassword $ telephoneNumber $ seeAlso $ description ) )

Note that there is also an 'olcObjectIdentifier' attribute type that seems to be used to create
macros for interpolation in OID's used in other attributes:

  olcObjectIdentifier: OLcfg
  olcObjectIdentifier: OLcfgAt OLcfg:3
  olcObjectIdentifier: OLcfgOvAt OLcfgAt:3
  olcObjectIdentifier: OMsyn
  olcObjectIdentifier: OMsBoolean OMsyn:7

  olcAttributeTypes: ( OLcfgOvAt:10.4 NAME 'olcUniqueStrict' DESC 'Enforce uniqueness of null
values' EQUALITY booleanMatch SYNTAX OMsBoolean SINGLE-VALUE )

However this additional complexity seems to only be used for the internal/vendor-specific
schema itself (not 'core', 'nis', etc.).

Attached is LDIF output of from searching cn=schema,cn=config.

Mailing List reference:

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message