[jira] Closed: (DIRSERVER-836) Requesting an unknown attribute in a search operation causes an error

["Stefan Zoerner (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/DIRSERVER-836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Stefan Zoerner closed DIRSERVER-836.
------------------------------------


I do confirm that it works with rev. 508131, well done, Emmanuel!

> Requesting an unknown attribute in a search operation causes an error
> ---------------------------------------------------------------------
>
>                 Key: DIRSERVER-836
>                 URL: https://issues.apache.org/jira/browse/DIRSERVER-836
>             Project: Directory ApacheDS
>          Issue Type: Bug
>    Affects Versions: 1.0.1
>         Environment: * ApacheDS 1.5.0 (SNAPSHOT)
> * Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_07-b03)
> * Windows XP Professional SP2
>            Reporter: Stefan Zoerner
>            Priority: Blocker
>             Fix For: 1.0.1
>
>         Attachments: SearchForNonExistingAttributesTest.java
>
>
> If someone tries to fetch an unknown attribute within a search operation, it causes an error. The expected behaviour is that the server ignores the unknown attribute. Here is a command line example:
> $ ldapsearch -h localhost -p 10389 -D "uid=admin,ou=system" -w ****** -b "dc=example,dc=com" -s base "(objectClass=*)" dc
> version: 1
> dn: dc=example,dc=com
> dc: example
> $ ldapsearch -h localhost -p 10389 -D "uid=admin,ou=system" -w ****** -b "dc=example,dc=com" -s base "(objectClass=*)" dc unknown
> ldap_search: Alias dereferencing problem
> ldap_search: additional info: failed on search operation: OID for name 'unknown' was not found within the OID registry
> $ ldapsearch -h localhost -p 10389 -D "uid=admin,ou=system" -w ******-b "dc=example,dc=com" -s base "(objectClass=*)" dc;unknownOption
> ldap_search: Alias dereferencing problem
> ldap_search: additional info: failed on search operation: OID for name 'dc;unknownOption' was not found within the OID registry
> $
> I'll attach a JUnit test which demonstrates the problem with the help of JNDI.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.