Bug 1515213 - Send password in API function for new user just once
Summary: Send password in API function for new user just once
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: web-admin-tendrl-api
Version: rhgs-3.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: RHGS 3.4.0
Assignee: Shirshendu Mukherjee
QA Contact: sds-qe-bugs
URL:
Whiteboard:
Depends On:
Blocks: 1503134
TreeView+ depends on / blocked
 
Reported: 2017-11-20 12:10 UTC by Filip Balák
Modified: 2018-09-04 06:59 UTC (History)
4 users (show)

Fixed In Version: tendrl-ansible-1.6.1-2.el7rhgs.noarch.rpm, tendrl-api-1.6.1-1.el7rhgs.noarch.rpm, tendrl-commons-1.6.1-1.el7rhgs.noarch.rpm, tendrl-monitoring-integration-1.6.1-1.el7rhgs.noarch.rpm, tendrl-node-agent-1.6.1-1.el7, tendrl-ui-1.6.1-1.el7rhgs.noarch.rpm,
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-09-04 06:58:45 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github Tendrl api issues 106 0 None closed send password in API function for new user just once 2020-10-21 05:18:31 UTC
Red Hat Bugzilla 1554882 0 unspecified CLOSED Password is sent twice from UI when user is created/edited 2021-02-22 00:41:40 UTC
Red Hat Product Errata RHSA-2018:2616 0 None None None 2018-09-04 06:59:57 UTC

Internal Links: 1554882

Description Filip Balák 2017-11-20 12:10:18 UTC
Description of problem:
Create user API call requires to specify parameters `password` and `password_confirmation`. There should be provided only `password` parameter and confirmation of matching passwords should be held on the front-end side.

Version-Release number of selected component (if applicable):
tendrl-selinux-1.5.3-2.el7rhgs.noarch
tendrl-commons-1.5.4-3.el7rhgs.noarch
tendrl-api-httpd-1.5.4-2.el7rhgs.noarch
tendrl-grafana-selinux-1.5.3-2.el7rhgs.noarch
tendrl-ansible-1.5.4-1.el7rhgs.noarch
tendrl-node-agent-1.5.4-3.el7rhgs.noarch
tendrl-ui-1.5.4-3.el7rhgs.noarch
tendrl-grafana-plugins-1.5.4-4.el7rhgs.noarch
tendrl-notifier-1.5.4-2.el7rhgs.noarch
tendrl-api-1.5.4-2.el7rhgs.noarch
tendrl-monitoring-integration-1.5.4-4.el7rhgs.noarch


How reproducible:
100%

Steps to Reproduce:
1. Check in Tendrl that there is no user called thardy.
2. Send API call like this (with valid access token):
```
curl -H 'Content-Type: application/json' -H 'Authorization: Bearer
d03ebb195dbe6385a7caeda699f9930ff2e49f29c381ed82dc95aa642a7660b8'
-XPOST -d '{"name":"Tom Hardy", "username":"thardy",
"email":"thardy", "role":"admin", "password":"pass1234",
"email_notifications": true}'
http://127.0.0.1/api/1.0/users
```
3. Send API call like this (with valid access token):
```
curl -H 'Content-Type: application/json' -H 'Authorization: Bearer
d03ebb195dbe6385a7caeda699f9930ff2e49f29c381ed82dc95aa642a7660b8'
-XPOST -d '{"name":"Tom Hardy", "username":"thardy",
"email":"thardy", "role":"admin", "password":"pass1234",
"password_confirmation":"pass1234","email_notifications": true}'
http://127.0.0.1/api/1.0/users
```

Actual results:
API call from step 2 fails because there was not provided parameter `password_confirmation`. API call from step 3 succeeds.

Expected results:
API call from step 2 should succeed.

Additional info:
https://github.com/Tendrl/api/blob/master/docs/users.adoc#create-user

Comment 3 Filip Balák 2018-03-13 14:15:14 UTC
Looks ok. --> VERIFIED
This should be handled also by UI. --> created BZ 1554882.

Tested with:
tendrl-ansible-1.6.1-2.el7rhgs.noarch
tendrl-api-1.6.1-1.el7rhgs.noarch
tendrl-api-httpd-1.6.1-1.el7rhgs.noarch
tendrl-commons-1.6.1-1.el7rhgs.noarch
tendrl-grafana-plugins-1.6.1-1.el7rhgs.noarch
tendrl-grafana-selinux-1.5.4-2.el7rhgs.noarch
tendrl-monitoring-integration-1.6.1-1.el7rhgs.noarch
tendrl-node-agent-1.6.1-1.el7rhgs.noarch
tendrl-notifier-1.6.0-1.el7rhgs.noarch
tendrl-selinux-1.5.4-2.el7rhgs.noarch
tendrl-ui-1.6.1-1.el7rhgs.noarch

Comment 5 errata-xmlrpc 2018-09-04 06:58:45 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2018:2616


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