You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@directory.apache.org by "Stefan Zoerner (JIRA)" <di...@incubator.apache.org> on 2006/01/20 15:42:42 UTC

[jira] Created: (DIREVE-327) Adding an entry with invalid attribute

Adding an entry with invalid attribute
--------------------------------------

         Key: DIREVE-327
         URL: http://issues.apache.org/jira/browse/DIREVE-327
     Project: Directory Server
        Type: Bug
    Versions: 0.9.4    
    Reporter: Stefan Zoerner
 Assigned to: Alex Karasulu 


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).


-- 
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

[jira] Resolved: (DIREVE-327) Adding an entry with invalid attribute

Posted by "Emmanuel Lecharny (JIRA)" <di...@incubator.apache.org>.

     [ http://issues.apache.org/jira/browse/DIREVE-327?page=all ]
     
Emmanuel Lecharny resolved DIREVE-327:
--------------------------------------

    Resolution: Fixed

The creation of an entry with an attribute which is not described in the schema is now not any more allowed.

> Adding an entry with invalid attribute
> --------------------------------------
>
>          Key: DIREVE-327
>          URL: http://issues.apache.org/jira/browse/DIREVE-327
>      Project: Directory Server
>         Type: Bug
>     Versions: 0.9.4
>     Reporter: Stefan Zoerner
>     Assignee: Alex Karasulu

>
> 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).

-- 
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

[jira] Closed: (DIRSERVER-329) Adding an entry with invalid attribute

Posted by "Stefan Zoerner (JIRA)" <ji...@apache.org>.

     [ http://issues.apache.org/jira/browse/DIRSERVER-329?page=all ]
     
Stefan Zoerner closed DIRSERVER-329:
------------------------------------


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.

> Adding an entry with invalid attribute
> --------------------------------------
>
>          Key: DIRSERVER-329
>          URL: http://issues.apache.org/jira/browse/DIRSERVER-329
>      Project: Directory ApacheDS
>         Type: Bug

>     Reporter: Stefan Zoerner
>     Assignee: Alex Karasulu

>
> 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).

-- 
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