Fetching the schema fails on some LDAP clients
----------------------------------------------
Key: DIREVE-227
URL: http://issues.apache.org/jira/browse/DIREVE-227
Project: Directory Server
Type: Bug
Versions: 0.9.2
Reporter: Stefan Zoerner
Assigned to: Alex Karasulu
Priority: Minor
Fetching the schema fails on some LDAP clients I tried. Some others are able to
retrieve a subset of the schema. E.g. Softerra LDAP Adminstrator displays some
object classes, some are missing (for instance top, inetOrgPerson). Therefore
the creation of entries by some GUI clients may not work (e.g. if the client
provides support by displaying required and optional attributes). This is
especially true for Softerra.
I am not 100% sure, but I assume the problem lies in in the textual
respresentation of schema elements in the schema subentry. Here is an example:
Objectclass "top" looks to client like this for Apache DS:
( 2.5.6.0 NAME 'top' DESC 'top of the superclass chain' STRUCTURAL MUST
objectClass MAY )
and like this for another server I checked:
( 2.5.6.0 NAME 'top' DESC 'Standard LDAP objectclass' ABSTRACT MUST objectClass
X-ORIGIN 'RFC 2256' )
I guess some tools have problems with the empty "MAY". The same is probably
true for empty "MUST" parts. Therfore inetOrgPerson does not appear in
Softerra, but person does (person has both MAY and MUST attributes).
The problen does not only occur in some GUI clients, but also in JNDI code, if
you use the schema functionality (for many of your users this may be more
critical). You find a JNDI example attached to this issue report which crashes
an Apache DS but runs without problems on other solutions. Maybe the JNDI
parser has the same problem with empty MUSTs and MAYs. Problem is comparable,
e.g. fetching "top" causes an exception, "person" does not.
Btw.: Within the JXplorer client there are no problems.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
