Spaces in PROVIDER_URL environment value seems to lead to problems

• Key: DIRSERVER-602
• Type: Bug
• Status: Closed
• Resolution: Won't Fix
• Priority: Major
• Assignee: Stefan Zoerner
• Reporter: Tony Blanchard
• Affects Version/s: 1.0-RC2

Environment

WIN XP
ACI Enabled
sun LdapCtxFactory

Description

I found that giving a PROVIDER_URL value like this : "ldap://localhost:389/ou=Mon entreprise,dc=fr" to the InitialDirContext constructor returned a DirContext with a currentDN attribute to :"ou=Mon".

Ex :
lEnv.put(...);
lEnv.put(Context.PROVIDER_URL, "ldap://localhost:389/ou=Mon entreprise,dc=fr");
lEnv.put(Context.INITIAL_CONTEXT_FACTORY, "com.sun.jndi.ldap.LdapCtxFactory");

try
{
      lContext = new InitialDirontext(lEnv);
}
  [ .... ]

As a result, I can not use correctly this context.

Comments

[Stefan Zoerner]

I have some questions.

How do you determine the "currentDN" from the DirContext?
Which JDK-Version do you use?
What happens, if you try this LDAP URL? (blank is encoded)
lEnv.put(Context.PROVIDER_URL, "ldap://localhost:389/ou=Mon%20entreprise,dc=fr");

Thanks in advance, Stefan

[Tony Blanchard]

Hi Stefan

the "CurrentDN" is shown in my netbeans 4.1 debugger.
My JDK version is 1.5.0_04
I have already tried to replace the blank char with "%20" but it made no difference.

If I search under the context I created with this problem, the exception returned by ApacheDs gives also an incomplete name as baseDN for the search operation.

Hope this help.
If you need another information, I will be there

[Emmanuel Lecharny]

As stated by RFC 2255 :

"Note that any URL-illegal characters (e.g., spaces), URL special
   characters (as defined in section 2.2 of RFC 1738) and the reserved
   character '?' (ASCII 63) occurring inside a dn, filter, or other
   element of an LDAP URL MUST be escaped using the % method described
   in RFC 1738 [5]"

So lEnv.put(Context.PROVIDER_URL, "ldap://localhost:389/ou=Mon entreprise,dc=fr"); is not valid.

However, the problem remains if it does not work with lEnv.put(Context.PROVIDER_URL, "ldap://localhost:389/ou=Mon%20entreprise,dc=fr"); , as Stefan said.

This has to be evaluated and fixed.

Do you have a full testcase, Tony? It can help a lot :)

Thanks for the report !

While trying to make a test case as asked by Emmanuel, I noticed my " " replacement was not compiled with my other dependencies.

I am really sorry for time loss.
In fact, replacing " " by "%20", as I made in code but as I did not compile correctly, works just fine.

Sorry again for the mistake...
This JIRA entry should be closed.

[Stefan Zoerner]

In order to reflect the comment from Tony, that encoding of the blank in the URL makes his situation work, I resolve this issue ("Won't fix").

[Emmanuel Lecharny]

closed