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 2057503 - Regression: [samba] winbind isn't able to refresh Kerberos tickets
Summary: Regression: [samba] winbind isn't able to refresh Kerberos tickets
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: samba
Version: 8.5
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Andreas Schneider
QA Contact: Denis Karpelevich
URL:
Whiteboard:
Depends On: 2057500
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-02-23 14:20 UTC by Andreas Schneider
Modified: 2022-05-10 16:50 UTC (History)
6 users (show)

Fixed In Version: samba-4.15.5-4.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 2057500
Environment:
Last Closed: 2022-05-10 15:28:04 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-113296 0 None None None 2022-02-23 14:29:59 UTC
Red Hat Issue Tracker SSSD-4352 0 None None None 2022-02-23 14:49:42 UTC
Red Hat Product Errata RHSA-2022:2074 0 None None None 2022-05-10 15:28:18 UTC
Samba Project 14979 0 None None None 2022-02-23 14:20:30 UTC

Description Andreas Schneider 2022-02-23 14:20:31 UTC
+++ This bug was initially created as a clone of Bug #2057500 +++

Description of problem:
winbindd of Samba fails to automatically refresh Kerberos tickets. When pam_winbind is getting them.

Winbind needs to be configured with `winbind refresh tickets = yes`

[global]
    security = ADS
    workgroup = SAMBA
    realm = SAMBA.ORG
    winbind refresh tickets = yes
    [..]

And pam_winbind needs to be configured with krb5_auth and krb5_ccache_type. This should be the case with if you use `realm join` or the winbind authselect profile.


How reproducible:


Steps to Reproduce:
1. Setup a Windows or Samba AD server
2. Change the 'Maximum lifetime for user ticket' Kerberos Policy (GPO) on the server and set it to 5 or 10 minutes (default should be 8 or 10 hours).
3. Configure a Domain member with `winbind refresh tickets = yes` and pam_winbind doing a krb5_auth
4. Login with ssh as a domain user
5. Check the liftime of the TGT with klist
6. Check again after 10 min that the ticket has been automatically renewed

Comment 7 errata-xmlrpc 2022-05-10 15:28:04 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 (Moderate: samba security, bug fix, and enhancement update), 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://access.redhat.com/errata/RHSA-2022:2074


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