[DIRSERVER-605] Inconsistent behavior with anonymous access

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Won't Fix
• Affects Version/s: 1.0-RC1, 1.5.0
• Component/s: core
• Assignee: Alex Karasulu
• Reporter: Endi S. Dewata
• Created: 30/Mar/06 07:17
• Updated: 18/Aug/06 05:13
• Resolved: 18/Aug/06 05:13

Description

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 (http://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.