Bug 38385 - users/user does not update displayName if firstname or lastname is modified
users/user does not update displayName if firstname or lastname is modified
Status: CLOSED FIXED
Product: UCS
Classification: Unclassified
Component: UMC - Users
UCS 4.0
Other Linux
: P5 normal (vote)
: UCS 4.0-3-errata
Assigned To: Sönke Schwardt-Krummrich
Daniel Tröder
:
Depends on:
Blocks: 39292 39409
  Show dependency treegraph
 
Reported: 2015-04-29 13:39 CEST by Sönke Schwardt-Krummrich
Modified: 2015-09-25 22:01 CEST (History)
3 users (show)

See Also:
What kind of report is it?: ---
What type of bug is this?: ---
Who will be affected by this bug?: ---
How will those affected feel about the bug?: ---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional): External feedback
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Sönke Schwardt-Krummrich univentionstaff 2015-04-29 13:39:02 CEST
The importscript create_ou and the UMC module "Users (schools)" do not update displayName if firstname or lastname is modified.

Reported by a customer.
Comment 1 Sönke Schwardt-Krummrich univentionstaff 2015-06-23 20:44:54 CEST
This issue is not solely UCS@school related and should be fixed in the UDM module users/user.

Ideally there is a heuristic that checks upon modification of firstname/lastname if the current LDAP value matches the automatically calculated value. If this is the case, displayName is updated together with firstname/lastname. If the current value does not match (user saved a different value), the displayName value is left untouched.
Comment 2 Sönke Schwardt-Krummrich univentionstaff 2015-08-25 12:25:19 CEST
In previous versions the user's display name has only been set automatically during user creation. When the first name or last name has been changed later on, the display name of the user has not been updated. 
univention-directory-manager-modules has been modified, so the display name is updated automatically upon change of first or last name if the display name contains still the default value that has been automatically created. If the display name has been altered manually and does not match the "default value", no automatic update is performed.

Additionally a ucs-test script has been added, that checks if
- the displayName is correctly created during user creation
- the displayName is correctly updated during user modification (if displayName 
  has not been altered); the test distinguishes between modifcation of a) first 
  name, b) last name, c) both
- the displayName is correctly set during user creation if first name, last 
  name AND a custom displayName is specified
- the displayName is not updated during user modification, if a custom 
  displayName has been set before and a) first name, b) last name or c) both 
  are modified.
The test fails, if not at least univention-directory-manager-modules (10.0.31-13) has been installed.

univention-directory-manager-modules (10.0.31-13):
r63218 | Bug #38385: update users/user's displayName property automatically upon change of its superordinate properties (per default firstname and lastname)

ucs-test (5.0.169-5):
r63219 | Bug #38385: added 28_displayName_update

2015-08-24-univention-directory-manager-modules.yaml:
r63237 | Bug #38385: updated YAML
r63220 | Bug #38385: added yaml for univention-directory-manager-modules
Comment 3 Daniel Tröder univentionstaff 2015-08-25 15:03:27 CEST
OK code : r63218
OK test : r63219 
OK YAML : r63220 & r63237
OK manual test
OK (provided) automatic test
Comment 4 Janek Walkenhorst univentionstaff 2015-08-27 18:14:24 CEST
<http://errata.univention.de/ucs/4.0/290.html>