Bug 1373111

Summary: Extend ovirt-aaa-jdbc-tool output to display current lock status on accounts
Product: Red Hat Enterprise Virtualization Manager Reporter: Gajanan <gchakkar>
Component: ovirt-engine-extension-aaa-jdbcAssignee: Ondra Machacek <omachace>
Status: CLOSED ERRATA QA Contact: Pavol Brilla <pbrilla>
Severity: medium Docs Contact:
Priority: high    
Version: 3.6.0CC: gklein, lsurette, melewis, mgoldboi, mperina, pbrilla, rbalakri, srevivo, tjelinek, ykaul
Target Milestone: ovirt-4.0.5Keywords: ZStream
Target Release: 4.0.5   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Previously, the current status of account lock was not displayed directly when showing user details using ovirt-aaa-jdbc-tool. The 'Account Unlocked At' date was compared with the current date and if 'Account Unlocked At' was set to future time the user account was locked. Now, the current status of account lock is displayed correctly. An "Account Locked' option with a boolean value has been added to the user details displayed by ovirt-aaa-jdbc-tools. For example: # ovirt-aaa-jdbc-tool user show user1 -- User user1(de506247-d1a1-4f16-94f3-0b83b0b236b2) -- Account Disabled: false Account Locked: true Account Unlocked At: 2016-09-09 11:42:25Z
 Story Points: ---
Clone Of: Environment:
Last Closed: 2016-11-16 15:31:57 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Infra RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Gajanan 2016-09-05 08:56:51 UTC 
====================== RFE TEMPLATE ========================

1. Proposed title of this feature request

Extend ovirt-aaa-jdbc-tool output to display current lock status on accounts


3. What is the nature and description of the request?

An active account was locked out. While the CLI output showed that the lockout had recently been reset, the account was in actual fact still locked out. Displaying the current lockout status of the account would immediately highlight the issue.


4. Why does the customer need this? (List the business requirements here)


5. How would the customer like to achieve this? (List the functional requirements here)

Add lockout status to the CLI output

6. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.

7. Is there already an existing RFE upstream or in Red Hat Bugzilla?

- No

8. Does the customer have any specific timeline dependencies and which release would they like to target ?

As soon as possible.

9. Is the sales team involved in this request and do they have any additional input?

- No

10. List any affected packages or components.

11. Would the customer be able to assist in testing this functionality if implemented?

Yes
Comment 2 Martin Perina 2016-09-12 12:35:30 UTC 
Fix will be included in ovirt-engine-extension-aaa-jdbc-1.1.1
Comment 3 Martin Perina 2016-10-11 14:40:27 UTC 
Fix is contained in ovirt-engine-extension-aaa-jdbc-1.1.1
Comment 5 Pavol Brilla 2016-10-18 06:13:28 UTC 
Build found in erratum: ovirt-engine-extension-aaa-jdbc-1.1.1-1.el7ev
Comment 6 Pavol Brilla 2016-10-18 06:14:18 UTC 
Wrong bug, please discard Verified status and last comment
Comment 7 Pavol Brilla 2016-10-18 08:05:39 UTC 
# ovirt-aaa-jdbc-tool user show admin | grep Locked
Account Locked: false

# yum list ovirt-engine-extension-aaa-jdbc
Installed Packages
ovirt-engine-extension-aaa-jdbc.noarch         1.1.1-1.el7ev         @4.0.5-2
Comment 9 errata-xmlrpc 2016-11-16 15:31:57 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://rhn.redhat.com/errata/RHBA-2016-2793.html