Bug 238282

Summary:	while changing the first or last name of ldap users, the cn is not updated
Product:	[openSUSE] openSUSE 11.1	Reporter:	Sebastian Reitenbach <reitenbach>
Component:	YaST2	Assignee:	Jiří Suchomel <jsuchome>
Status:	RESOLVED WONTFIX	QA Contact:	Jiri Srain <jsrain>
Severity:	Enhancement
Priority:	P4 - Low	CC:	paul.zirnik
Version:	Alpha 0
Target Milestone:	Alpha 0
Hardware:	x86-64
OS:	openSUSE 11.0
Whiteboard:
Found By:	Customer	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Attachments:	the wanted log file

Description Sebastian Reitenbach 2007-01-24 17:03:48 UTC

As the cn entry in ldap consists of a first name and last name, it should get updated when the first name or last name of the user is changed.

Many services use the cn, and not the first and last name fields from the ldap server, and therefore present the "not updated", plain wrong, values.

as far as I can see, the uid is the field to distinguish users, it shouldn't be a problem to change the cn.

Comment 1 Matej Horvath 2007-01-26 19:10:28 UTC

Just to be sure: do you mean the yast ldap configuration utility?

Comment 2 Sebastian Reitenbach 2007-01-29 08:07:04 UTC

yes, I mean this. start yast2, go to security and users, -> user configuration, and set the filter to ldap users.

Comment 3 Cyril Hrubis 2007-01-29 14:09:33 UTC

Please attach y2logs. If you are in doubt please follow:

http://en.opensuse.org/Bugs/YaST


Thanks!

Comment 4 Sebastian Reitenbach 2007-01-29 15:53:13 UTC

Created attachment 115920 [details]
the wanted log file

the sn of the user sre was changed from Reitenbach to ReitenbachTEST, but the cn: was not updated

Comment 5 Jiří Suchomel 2007-01-30 10:31:14 UTC

The forming of new values based on some other ones is based on the content of suseUserTemplate object (suseDefaultValue attributes, e.g. "cn=%givenname %sn" or  
homedirectory=/home/%uid).

However, these rules are applied only on creating new user, not on editing. When editing. I'm not sure if user wouldn't rather leave the old settings and only let change those that were changed manually.

Ralf, what do you think?

Comment 6 Ralf Haferkamp 2007-01-30 10:59:18 UTC

Hard to tell. As it is pretty awkward for the user to change the "cn" Attribute. (IIRC he has to go to the plugin tab, start the LDAP Attribute Plugin and edit the "cn" there).

On the other hand just updating the "cn" in any case can have very strange and non-obvious effects for the user of yast2-users. E.g. if I change the "uid" Attribute the "homedirectory"-Attribute will also get update. In most cases that's not what the user indented.

The best would probably be to offer a more convenient way to edit a user's LDAP Attributes. I just don't have an idea yet, how that could work without throwing the idea of having the dialogs for local and LDAP users as similar as possible over board.

But I digress a bit ;). To come back to the main question. I think the attribute should not automagically be updated when editing a user, for the above mention reasons.

Comment 7 Sebastian Reitenbach 2007-01-30 11:45:48 UTC

after changing fields that might result in changes of other fields, maybe let just an popup appear, stating that the field XY was changed, and whether fields depending on them should be changed too?

Comment 8 Jiří Suchomel 2007-01-30 12:36:14 UTC

Maybe that can be solution.

Comment 11 Stanislav Visnovsky 2008-05-26 09:13:00 UTC

Moving to 11.1.

Comment 12 Jiří Suchomel 2009-02-04 09:28:22 UTC

I probably can't find a time for this.

Comment 13 Jiří Suchomel 2013-09-26 12:37:54 UTC

*** Bug 842491 has been marked as a duplicate of this bug. ***