Closed
Bug 466400
Opened 16 years ago
Closed 16 years ago
Can't do LDAP lookup of Active Directory with Japanese (Unicode) characters in Base DN
Categories
(Thunderbird :: Address Book, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 389655
People
(Reporter: ces-mozillabugs, Unassigned)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9.0.4) Gecko/2008102920 Firefox/3.0.4
Build Identifier: version 2.0.0.18 (20081105)
I'm working in Japan. I would like to look-up addresses in my company's Active Directory.
The problem is, the relevant "Base DN" has Japanese text in it. When I try to put it in the "Base DN" field of the configuration dialog box, it looks fine, but after I click okay, then try to open the dialog again, all the fields have become empty.
E.g.:
OU=車載,OU=裾野,OU=管理,DC=department1,DC=local
Alternatively, if I try a shorter variation of the Base DN, it will clear the Base DN to simply "OU=" and leave the other fields intact. E.g.:
OU=管理,DC=department1,DC=local
I can do look-ups of the LDAP server just fine using the following Java tool:
http://www-unix.mcs.anl.gov/~gawor/ldap/applet/applet.html
Reproducible: Always
Steps to Reproduce:
1. Create a new LDAP Directory in the address book window
2. Fill out various details in the fields.
3. For the "Base DN" field, enter:
OU=車載,OU=裾野,OU=管理,DC=department1,DC=local
4. Click okay.
5. Double-click on the LDAP directory just created. Observe that most fields have been blanked.
Alternatively:
3. For the "Base DN" field, enter:
OU=管理,DC=department1,DC=local
4. Click okay.
5. Double-click on the LDAP directory just created. Observe that the Base DN field only contains "OU=".
Actual Results:
Resulting LDAP directory lookup fields are blank, or the Base DN field is truncated.
Expected Results:
LDAP Directory configuration fields should contain text as entered.
Reporter | ||
Updated•16 years ago
|
Version: unspecified → 2.0
Reporter | ||
Comment 1•16 years ago
|
||
A little related: bug #151448
Comment 2•16 years ago
|
||
This has already been fixed for the next major version of Thunderbird (3).
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•