LDAP and user names with umlauts




9 years ago
9 years ago


(Reporter: nico.schloemer, Unassigned)





9 years ago
User-Agent:       Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv: Gecko/2009033114 Gentoo Firefox/3.0.8
Build Identifier: 


I just started up my first bugzilla here and had it connect to an LDAP server.

I noticed that, when a user name is, say, Sörname, bugzilla will display it as Sörname.

Not sure how I can help debugging this, so let me know.


Reproducible: Always

Comment 1

9 years ago
Thanks for the report.

What version of Bugzilla are you using? Is the utf8 parameter turned on? What type and version of LDAP server are you connecting to?

Comment 2

9 years ago
I'm on Buzilla 3.2.3 here, with UTF-8 turned on.

When playing around with Bugzilla I notice that the umlaut comes out alright in most places, in fact the only page where I've seen the "Sörname" now was that welcome page for the first user telling you that not all parameters have been set yet.

If that still matters, I *think* that the people here use ActiveDirectory LDAP, no idea about any specific version.

Comment 3

9 years ago
Oh, was that user that you're seeing actually created out of LDAP, or was that the user that was created by checksetup.pl?

Comment 4

9 years ago
Well, yes and no.

The user I first created in Bugzilla had the e-mail address john@doe.com. This happens to be the e-mail address associated with the LDAP account I logged in with ('mail' field) -- I understand that the "two" accounts get merged in that case.

Anyway, the "Sörname" is fetched from LDAP's 'displayName' field.

-- But, as I said, it seems to be translated quite correctly except on the start page (which I can't access anymore now b/c I set all the parameters).

Comment 5

9 years ago
Okay, so we'll mark this as WORKSFORME unless it pops up again somewhere somehow.
Last Resolved: 9 years ago
Resolution: --- → WORKSFORME
For note, I now properly operating on utf8's display name with integrating OpenLDAP. (using syncLDAP.pl)
You need to log in before you can comment on or make changes to this bug.