286548 - user_pref "ldap_2.servers.something.auth.dn" is not written correctly if DN contains greek characters

Status: RESOLVED EXPIRED

(Thunderbird :: Preferences, defect)

Description

[Dimitris Xenakis]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.6) Gecko/20050225 Firefox/1.0.1 StumbleUpon/1.9992
Build Identifier: Thunderbird version 1.0 (20041206)

I cannot query our internal LDAP directory, as it requires authentication but
the DN in our case contains greek characters, and somewhere in the process the
correct characters are replaced by gibberish. I think the giberish is sent to
the server, the server denies access and so no success.

The LDAP server works as expected when I enter the same information through
other clients, i.e. not Thunderbird.

Reproducible: Always

Steps to Reproduce:
1. Menu Tools/Options/Composition Button "Edit Directories", Add 
2. Enter non-ascii (in my case Greek) characters for Bind DN (e.g. "CN=Καλημέρα,
OU=Λογιστήριο" and so on) then OK everything to go back to TB
3. Exit Thunderbird to make sure prefs.js is written
4. Open prefs.js, check line: user_pref("ldap_2.servers.myserver.auth.dn",
"CN=±»·Ό­Α±, OU=›Ώ³ΉΓΔ®ΑΉΏ");


Actual Results:  
cannot query ldap addressbook, nothing is returned, no message by the software.

Expected Results:  
list of people I would like to send mail to.

One can see there is something wrong even before exiting and checking prefs.js:
After step 2 above, one can re-open (by editing) the relevant ldap entry and the
Bind DN has disappeared. This is not the behaviour that is expected, and is not
what happens when an ASCII Bind DN is entered.

Comment 1

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 2

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.