Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 828865

Summary: [RFE] Allow quering user lock status
Product: Red Hat Enterprise Linux 8 Reporter: Dmitri Pal <dpal>
Component: ipaAssignee: IPA Maintainers <ipa-maint>
Status: CLOSED WONTFIX QA Contact: IDM QE LIST <seceng-idm-qe-list>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 8.0CC: abokovoy, bbenson, cheimes, cpatil, ipa-maint, jgalipea, mkosek, mtessun, mvarun, nathan.t.mcgarvey, pasik, patdung100+redhat, pcech, pvoborni, rcritten, steven.r.coleman, suwu, tscherf
Target Milestone: rcKeywords: FutureFeature
Target Release: 8.0Flags: dpal: mirror+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-07-10 06:11:40 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1113520    

Description Dmitri Pal 2012-06-05 13:41:56 UTC
This bug is created as a clone of upstream ticket:
https://fedorahosted.org/freeipa/ticket/2792

In the UI probably in the details page there should be some kind of place when admin can click to see what is the status of the current user in terms of lockout. I see it as a subsection that expends in a list that contains following columns:
{{{
Name      Status       Failed attempts   Will unlock in 
replica1  Unlocked     0                 
replica2  Unlocked     2
replica3  Locked       3                 3 hours 26 minutes 16 sec
}}}

The locked status will be a clicable link that will pop up a confirmation dialog and would allow user to unlock the user on the specific server.
There should also be a refresh button to reacquire the status from the servers.
If replica can't be accessed it should say "Unreachable".
This should be a link to and clicking this link would act as refresh of this specific replica status.

Comment 2 Martin Kosek 2014-06-27 12:06:33 UTC
Upstream RFE was re-scoped to deal with the user lock status page only. As such, it is targeted on further release (FreeIPA 4.3, currently).

Comment 3 Martin Kosek 2014-06-27 12:07:10 UTC
New button for unlocking user status *on one server* is tracked in:
https://fedorahosted.org/freeipa/ticket/4407

Comment 4 Martin Kosek 2014-12-16 11:45:22 UTC
*** Bug 1164242 has been marked as a duplicate of this bug. ***

Comment 11 Petr Vobornik 2018-03-20 17:11:35 UTC
*** Bug 1550207 has been marked as a duplicate of this bug. ***

Comment 17 Chetan Patil 2019-11-08 09:32:31 UTC
I have a customer whose having same query,we have proposed below solution.

`ipa user-status $user` command which has output like:

```
$ ipa user-status admin
-----------------------
Account disabled: False
-----------------------
  Server: server1.test.example.com
  Failed logins: 0
  Last successful authentication: N/A
  Last failed authentication: 20191005155059Z
  Time now: 2019-10-16T12:32:10Z
----------------------------
Number of entries returned 1
----------------------------

Is there anyway we can somehow script a way to externally force the sync of these locked users, even on some level of a periodic basis?
AKA:
First, query for locked users
Then, push then push lock to other LDAP servers.
Possibly via a cron job?

Comment 19 Petr Čech 2020-07-10 06:11:40 UTC
Thank you taking your time and submitting this request for Red Hat Enterprise Linux. The request was cloned to the upstream tracker a long time ago (see link to the upstream ticket above), but it was unfortunately not given priority either in the upstream project, nor in Red Hat Enterprise Linux.

Given that this request is not planned for a close release, it is highly unlikely it will be fixed in this major version of Red Hat Enterprise Linux. We are therefore closing the request as WONTFIX.

To request that Red Hat reconsiders the decision, please reopen the Bugzilla with the help of Red Hat Customer Service and provide additional business and/or technical details about it's importance to you. Please note that you can still track this request or even offer help in the referred upstream Pagure ticket to expedite the solution.

Comment 20 Red Hat Bugzilla 2023-09-18 00:10:26 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days