Inconsistent behavior with anonymous access
-------------------------------------------

Key: DIRSERVER-605
URL: http://issues.apache.org/jira/browse/DIRSERVER-605
Project: Directory ApacheDS
Type: Bug
Components: core
Versions: 1.0-RC1, 1.1.0
Reporter: Endi S. Dewata


Searching the Root DSE as an anonymous user using different clients produces
 inconsistent results.

The tests were performed using Sun's JNDI client and Novell's Java LDAP client (ht
tp://www.openldap.org/jldap). Please the notes in the attached test case for
 more details.

On ApacheDS 1.0-RC1 with allowAnonymousAccess=true the results are:
- JNDI Client    : pass
- V2 JNDI Client : pass
- V3 JNDI Client : pass
- LDAP Client    : pass
- V2 LDAP Client : pass
- V3 LDAP Client : pass
In this scenario everything passes as expected.

On ApacheDS 1.0-RC1 with allowAnonymousAccess=false the results are:
- JNDI Client    : pass
- V2 JNDI Client : pass
- V3 JNDI Client : fail
- LDAP Client    : fail
- V2 LDAP Client : pass
- V3 LDAP Client : pass
In this scenario everything was expected to fail.

On ApacheDS 1.1 with allowAnonymousAccess=true the results are:
- JNDI Client    : pass
- V2 JNDI Client : fail
- V3 JNDI Client : pass
- LDAP Client    : pass
- V2 LDAP Client : fail
- V3 LDAP Client : pass
In this scenario everything was expected to pass.

On ApacheDS 1.1 with allowAnonymousAccess=false the results are:
- JNDI Client    : pass
- V2 JNDI Client : fail
- V3 JNDI Client : fail
- LDAP Client    : fail
- V2 LDAP Client : fail
- V3 LDAP Client : pass
In this scenario everything was expected to fail.


--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secur...nistrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira

[ Post a follow-up to this message ]