Bug 28

Summary:	Wrong character encoding
Product:	Websites	Reporter:	Jérôme Hénin <heninj>
Component:	identity.mageia.org	Assignee:	Romain d'Alverny <rdalverny-OLD>
Status:	RESOLVED FIXED	QA Contact:
Severity:	minor
Priority:	Normal	CC:	atelier-bugs, bgmilne, misc
Version:	trunk
Target Milestone:	---
Hardware:	All
OS:	Linux
Whiteboard:
Source RPM:		CVE:
Status comment:

Description Jérôme Hénin 2011-02-15 10:54:02 CET

When I edit my account parameters on identity.mageia.org, the accents in my full name end up mangled, as if a UTF-8 string was interpreted
as iso-8859-1, then re-encoded as UTF-8, or something like that.

Comment 1 Jérôme Hénin 2011-02-15 10:56:48 CET

(In reply to comment #0)
> When I edit my account parameters on identity.mageia.org, the accents in my
> full name end up mangled, as if a UTF-8 string was interpreted
> as iso-8859-1, then re-encoded as UTF-8, or something like that.

Now that the bug is submitted, I can see on the bugzilla page that my name is stored correctly in the database, so it is only a problem with the display on identity.mageia.org. For that reason, I am reducing the severity of this bug to minor.

Severity: normal => minor

Comment 2 Michael Scherer 2011-02-15 11:58:04 CET

This should be fixed in trunk , try https://identity-trunk.mageia.org/

CC: (none) => misc

Comment 3 Jérôme Hénin 2011-02-15 12:07:27 CET

If I change the name field and click "update", I get an "Insufficient access" error. Also, what is the "add" button for? It doesn't seem to do much.

Comment 4 Michael Scherer 2011-02-15 12:24:47 CET

The add button on what form ?

Comment 5 Jérôme Hénin 2011-02-15 12:40:42 CET

I am talking about the Add button next to the 'cn' attribute, on the form at https://identity-trunk.mageia.org/user

Comment 6 Michael Scherer 2011-02-15 12:48:30 CET

The generated form is a automatic one, so it can be used with any type of ldap. I was planning to work on a better form ( ie, a non automatic one that will work with a specific usecase ), but didn't finish anything. So yes, the various button should disappear, but this is not related to this bug report ( which is about character encoding ).

Comment 7 Buchan Milne 2011-02-16 10:32:49 CET

Can we confirm that the names are displayed correctly at https://identity-trunk.mageia.org ? You should not need to change anything ....

(Attribute changes do work from CatDap, whether they work against Mageia's internal LDAP server is a different issue).

CC: (none) => bgmilne

Comment 8 Jérôme Hénin 2011-02-16 11:21:14 CET

(In reply to comment #7)
> Can we confirm that the names are displayed correctly at
> https://identity-trunk.mageia.org ? You should not need to change anything ....

Yup! Now the display is fine. Thanks!

I am marking this as fixed. I suppose the "Insufficient access" error will be addressed when misc's work comes to fruition.

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

Comment 9 Buchan Milne 2011-02-16 14:00:19 CET

The 'Insufficient access' error is provided directly by LDAP, and is not affected at all by the application.

So ... there is a disconnect between the LDAP ACLs and what the application is configured to allow users to edit. But, the idea was to allow users to edit most personal information.

I have updated the LDAP ACLs to allow users to modify their own cn,sn,givenName attributes.