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 1287119 - RFE: please add support for TGT lifetime notifications
Summary: RFE: please add support for TGT lifetime notifications
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: krb5-auth-dialog
Version: 6.8
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Alexander Larsson
QA Contact: BaseOS QE Security Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-12-01 14:34 UTC by Ondrej
Modified: 2017-12-06 11:59 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-12-06 11:59:47 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Ondrej 2015-12-01 14:34:05 UTC
Description of problem:
Currently, krb5-auth-dialog only supports notifications based on expiring TGTs. In our case TGT never expires as it is being automatically renewed by the SSSD daemon - until it hits the lifetime period.

It would be therefore more beneficial if we could configure krb5-auth-dialog the way that it warns user that the Kerberos ticket lifetime is approaching.

Also in cases where user has obtained a renewable TGT, this dialog should not prompt for password - instead it should perhaps offer a possibility to perform renewal on user behalf automatically.

Comment 2 Jakub Hrozek 2015-12-01 16:03:14 UTC
This would be best served by the InfoPipe API of SSSD and overall the desktop integration Alexander is working on.

Comment 3 Ondrej 2015-12-01 18:51:20 UTC
That would, indeed. But that seems to be quite a long run project which will hardly make it into RHEL-7. What I am looking for here is something quick and relatively easy fix for RHEL-6 and/or 7 which can serve in the mean time.

Comment 4 Jan Kurik 2017-12-06 11:59:47 UTC
Red Hat Enterprise Linux 6 is in the Production 3 Phase. During the Production 3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available.

The official life cycle policy can be reviewed here:

http://redhat.com/rhel/lifecycle

This issue does not meet the inclusion criteria for the Production 3 Phase and will be marked as CLOSED/WONTFIX. If this remains a critical requirement, please contact Red Hat Customer Support to request a re-evaluation of the issue, citing a clear business justification. Note that a strong business justification will be required for re-evaluation. Red Hat Customer Support can be contacted via the Red Hat Customer Portal at the following URL:

https://access.redhat.com/


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