Issue Details (XML | Word | Printable)

Key: DIRSERVER-329
Type: Bug Bug
Status: Closed Closed
Resolution: Fixed
Priority: Major Major
Assignee: Alex Karasulu
Reporter: Stefan Zoerner
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
Directory ApacheDS

Adding an entry with invalid attribute

Created: 20/Jan/06 11:42 PM   Updated: 25/Jun/06 07:05 PM
Return to search
Component/s: None
Affects Version/s: None
Fix Version/s: None

Time Tracking:
Not Specified

Issue Links:
Blocker
 

Resolution Date: 30/Jan/06 08:34 AM


 Description  « Hide
This is related to DIRLDAP-84. We had a discussion about it on the mailing list and I want to be sure it is filed in JIRA. Therefore I open a separate issue.

The following entry can be created (note that attribute "voice" does not exist in the schema).

dn: cn=Kate Bush,dc=example,dc=com
cn: Kate Bush
objectclass: top
objectclass: person
sn: Bush
voice: unbelievable

The following operation does neither throw an error nor an exception on
server side

$ ldapadd -p 10389 -D uid=admin,ou=system -w ***** -f addKate.ldif
adding new entry cn=Kate Bush,dc=example,dc=com

But searching Kate causes exceptions on the server (not visible to the
client) like

javax.naming.NamingException: OID for name 'voice' was not found within the
OID
registry
        at
org.apache.ldap.server.schema.GlobalOidRegistry.getOid(GlobalOidRegistry.java:176)
        at
org.apache.ldap.server.schema.GlobalAttributeTypeRegistry.lookup(GlobalAttributeTypeRegistry.java:124)
        at
org.apache.ldap.server.partition.impl.btree.BTreeSearchResultEnumeration.next(BTreeSearchResultEnumeration.java:181)
        at
org.apache.ldap.server.enumeration.SearchResultFilteringEnumeration.prefetch(SearchResultFilteringEnumeration.java:299)
        at
org.apache.ldap.server.enumeration.SearchResultFilteringEnumeration.<init>(SearchResultFilteringEnumeration.java:110)
        at
org.apache.ldap.server.collective.CollectiveAttributeService.search(CollectiveAttributeService.java:279)
        at
org.apache.ldap.server.interceptor.InterceptorChain$Entry$1.search(InterceptorChain.java:1178)
        at
org.apache.ldap.server.operational.OperationalAttributeService.search(OperationalAttributeService.java:255)

and it is not possible to change the entry afterwards (DIRLDAP-84).


 All   Comments   Work Log   Change History   Subversion Commits      Sort Order: Ascending order - Click to sort in descending order
Stefan Zoerner added a comment - 24/Jan/06 11:12 PM
I think the origin of this issue is the creation of an invalid entry. This is described in DIREVE-327.

Stefan Zoerner made changes - 24/Jan/06 11:12 PM
Field Original Value New Value
Link This issue is blocked by DIRLDAP-84 [ DIRLDAP-84 ]
Emmanuel Lecharny added a comment - 30/Jan/06 08:34 AM
The creation of an entry with an attribute which is not described in the schema is now not any more allowed.

Emmanuel Lecharny made changes - 30/Jan/06 08:34 AM
Status Open [ 1 ] Resolved [ 5 ]
Resolution Fixed [ 1 ]
Alex Karasulu made changes - 10/Feb/06 12:34 PM
Project Directory Server [ 10516 ] Directory ApacheDS [ 12310260 ]
Affects Version/s 1.0-RC1 [ 12310230 ]
Key DIREVE-327 DIRSERVER-329
Stefan Zoerner added a comment - 25/Jun/06 07:05 PM
Retested with the example data given in the description, Softerra LDAP Administrator 3.1 and ApacheDS 1.0 RC3. It worked as expected (entry creation failed), therefore I close this issue.

Stefan Zoerner made changes - 25/Jun/06 07:05 PM
Status Resolved [ 5 ] Closed [ 6 ]