Bug 881549 - [RFE] Allow admins to change account user names.
[RFE] Allow admins to change account user names.
Status: CLOSED CURRENTRELEASE
Product: Zanata
Classification: Community
Component: Component-Logic (Show other bugs)
2.0
Unspecified Unspecified
unspecified Severity medium
: ---
: 2.1
Assigned To: Carlos Munoz
Ding-Yi Chen
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2012-11-28 23:42 EST by Carlos Munoz
Modified: 2013-02-25 23:06 EST (History)
1 user (show)

See Also:
Fixed In Version: 2.1-SNAPSHOT (20121211-1215)
Doc Type: Enhancement
Doc Text:
Feature: Administrators can now change an account's username. Reason: In some scenarios, some users need to change their username and Zanata did not offer a way to do this. Result (if any): User names can now be changed provided they remain unique throughout the system.
Story Points: ---
Clone Of:
Environment:
Last Closed: 2013-02-25 23:06:18 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Carlos Munoz 2012-11-28 23:42:35 EST
Allow administrators to change account user names.

This will be useful when testing user account creation in Kerberos authenticated systems.
Comment 2 Ding-Yi Chen 2012-12-03 23:05:49 EST
Tested with Zanata version 2.1-SNAPSHOT (20121204-0903)

If we change the user name but not the password, the user cannot continue to use they password to sign in. Admin does need to either provide a password or send a courtesy/confirmation email to user to 

Action item:
After username is changed, zanata should send a courtesy email such as:
Subject: Zanata: Username has changed to XXXX
Hi,

Your username has been changed to XXXX. Please go to the zanata server 
<ZanataServerUrl> to reset your password.


Reassigned.
Comment 3 Carlos Munoz 2012-12-06 00:26:41 EST
Zanata now sends an email when the username has been changed by an administrator. This only happens for instances where internal authentication is enabled. Other instances have no need to reset the user's password.

See:
https://github.com/zanata/zanata/commit/0fdc1ae289a0a6e9aa605cb28fcd045b1da21bcb
Comment 4 Ding-Yi Chen 2012-12-10 22:09:57 EST
VERIFIED with Zanata version 2.1-SNAPSHOT (20121211-1215)

Note You need to log in before you can comment on or make changes to this bug.