Bug 1654623 - Edited user can't log in
Summary: Edited user can't log in
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: web-admin-tendrl-ui
Version: rhgs-3.4
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: ---
Assignee: Neha Gupta
QA Contact: sds-qe-bugs
Depends On:
Blocks: 1654743
TreeView+ depends on / blocked
Reported: 2018-11-29 09:27 UTC by Elena Bondarenko
Modified: 2019-08-14 05:54 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2019-08-14 05:54:46 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github Tendrl ui issues 1091 0 None None None 2018-12-06 04:05:02 UTC
Red Hat Bugzilla 1610660 0 unspecified CLOSED New user can be created with Update user API call 2021-02-22 00:41:40 UTC

Internal Links: 1610660

Description Elena Bondarenko 2018-11-29 09:27:58 UTC
Description of problem:

After a user edits their username in My Settings they can't log in anymore because their password is simultaneously changed to empty string, and the login page won't allow to log in with the empty Password text box.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:

1. Log in
2. Click My Settings 
3. Enter a new name in Name text box
4. Save changes
5. Log out
6. Try to log in again

Actual results:

It's impossible to log in because the password has been changed to empty string.

Expected results:

Changing user's name doesn't cause the change of password. It's possible to log in after the change of user's name with the old password.

Additional info:

The json in the POST request when a user edits their name includes 'password: ""'. It shouldn't.

Comment 2 Elena Bondarenko 2018-11-29 11:30:13 UTC
Zero-length password is also set if a user enables or disables their email notifications in My Settings or edits their e-mail address.

Comment 4 Nishanth Thomas 2019-08-14 05:54:46 UTC
Edit username is not a common usecase and low priority issue.Right now we don't have resources to pursue this.

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