Bug 20686

When logging in, Bugzilla gets the user name from identity.mageia.org and uses it to update the real name stored in Bugzilla. Said differently, changes made in Bugzilla are lost every time you log in.

I see two problems here:

1) Updating the real name in Bugzilla should be propagated to identity.mageia.org (the cn field), or Bugzilla should only take the name given by identity.m.o into account when logging into Bugzilla for the very first time.

2) I don't know which DB identity.m.o is using, but it seems data are not stored as UTF8. Could a sysadmin check this?

(In reply to Frédéric Buclin from comment #0)
> But when I log out and then log in again, my name is set back to "Frédéric".

I didn't smoke anything, but I patched Bugzilla to automatically convert "\xc3\xa9" into "\xe9" in comments, which is why you see my name correctly encoded in comment 0. :)


(In reply to Frédéric Buclin from comment #1)
> 1) Updating the real name in Bugzilla should be propagated to
> identity.mageia.org (the cn field), or Bugzilla should only take the name
> given by identity.m.o into account when logging into Bugzilla for the very
> first time.

I reported this problem upstream, see https://bugzilla.mozilla.org/show_bug.cgi?id=1356897. My preferred solution is to allow users to have a different real name in Bugzilla and in LDAP.

See Also: (none) => https://bugzilla.mozilla.org/show_bug.cgi?id=1356897

(In reply to Frédéric Buclin from comment #1)
> 2) I don't know which DB identity.m.o is using, but it seems data are not
> stored as UTF8. Could a sysadmin check this?

Data in LDAP (via identity.m.o) is fine. I tested locally with both Bugzilla 5.0.3 and 5.1.1, and the problem only occurs with PostgreSQL, not with MySQL/MariaDB. Still investigating...

commit aa57f25e629ad052b33d66635e5430d34f4c5f81
Author: Frédéric Buclin <LpSolit@...>
Date:   Mon Apr 17 19:20:25 2017 +0200

    Correctly decode LDAP data (mga#20686)
---
 Commit Link:
   http://gitweb.mageia.org/web/bugs/commit/?id=aa57f25e629ad052b33d66635e5430d34f4c5f81

The decoding issue is fixed! The realname being lost every time you log in is much less critical and is not a regression.

Resolution: (none) => FIXED
Status: ASSIGNED => RESOLVED