Bug 1299793 - When changing password, ovirt-aaa-jdbc-tools doesn't ask for password confirmation
Summary: When changing password, ovirt-aaa-jdbc-tools doesn't ask for password confirm...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine-extension-aaa-jdbc
Classification: oVirt
Component: Core
Version: 1.0.1
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ovirt-3.6.3
: 1.0.6
Assignee: Martin Perina
QA Contact: Ondra Machacek
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-01-19 09:41 UTC by Martin Perina
Modified: 2016-02-17 07:34 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-02-17 07:34:49 UTC
oVirt Team: Infra
Embargoed:
rule-engine: ovirt-3.6.z+
rule-engine: exception+
mgoldboi: planning_ack+
oourfali: devel_ack+
pstehlik: testing_ack+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 52802 0 master MERGED core: Add password confirmation to password-reset 2016-01-27 13:29:14 UTC
oVirt gerrit 52803 0 ovirt-engine-extension-aaa-jdbc-1.0 MERGED core: Add password confirmation to password-reset 2016-01-27 14:05:39 UTC

Description Martin Perina 2016-01-19 09:41:42 UTC 
Description of problem:

When changing password, ovirt-aaa-jdbc-tools doesn't ask for password confirmation, so it's easy to make a mistake.

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

ovirt-engine-extension-aaa-jdbc-1.0.1

How reproducible:

100%

Steps to Reproduce:
1. Execute 
  ovirt-aaa-jdbc-tool user password-reset admin


Actual results:

ovirt-aaa-jdbc-tool doesn't ask for password confirmation

Expected results:

ovirt-aaa-jdbc-tool should ask for password confirmation

Additional info:
Comment 1 Martin Perina 2016-01-28 09:39:42 UTC 
Fix will be included in ovirt-engine-extension-aaa-jdbc-1.0.6
Comment 2 Gil Klein 2016-02-17 07:34:49 UTC 
This bug was fixed and is slated to be in the upcoming version. As we
are focusing our testing at this phase on severe bugs, this bug was
closed without going through its verification step. If you think this
bug should be verified by QE, please set its severity to high and move
it back to ON_QA
Note You need to log in before you can comment on or make changes to this bug.