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.

Description of problem:

Sometimes it is useful to allow a specific user to log in exactly once (or a defined number of times) and lock the user afterwards. 


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

Use cases:

An external employee needs to be allowed to log in to a system just once to do perform a particular task.

Together with the Time-Based Account Policies as described in upstream ticket https://fedorahosted.org/freeipa/ticket/547 it would provide better control over not-so-trusted external users.

Against this would be: If a user logs in once, the Kerberos Ticket is still valid for some time.

The use case looks very similar to bug 1346935. What is the difference from practical perspective? To me it seems that bug 1346935 would handle use case of this bug better provided that it would be allowed for some time period.

Number of login attempts is quite limiting. The user then cannot have multiple sessions open, cannot reconnect if disconnected due to network issue or timeout or some other reason. Is it desired?

Upstream ticket:
https://fedorahosted.org/freeipa/ticket/5994

We are going to push this to upstream and roll in when that work is done.

Closing UPSTREAM