Bug 1905927

Summary:	[RFE] update keytab entries when renewing the machine account password
Product:	Red Hat Enterprise Linux 8	Reporter:	Sumit Bose <sbose>
Component:	samba	Assignee:	Pavel Filipensky <pfilipen>
Status:	CLOSED MIGRATED	QA Contact:	Denis Karpelevich <dkarpele>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	8.4	CC:	aboscatt, asn, dkarpele, gdeschner, pfilipen, thalman
Target Milestone:	rc	Keywords:	FutureFeature, MigratedToJIRA, Reopened, Triaged
Target Release:	8.0	Flags:	pm-rhel: mirror+
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	review
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-09-05 12:19:51 UTC	Type:	Story
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:	2211854

Description Sumit Bose 2020-12-09 10:52:10 UTC

Description of problem:
Current, when automatically updating the machine account password winbind only add the new password to the secrets.tdb but does not update the Kerberos keys in the keytab which are derived from the machine account password. As a result, after the update the keytab entries can neither be used for authentication nor to uncrypt and verify server tickets.

If 'kerberos method = secrets and keytab' (and maybe for 'system keytab' or 'dedicated keytab' as well?) winbind should create new entries in the keytab with updated KVNO and new hashes derived from the new machine account password.

Upstream ticket: https://bugzilla.samba.org/show_bug.cgi?id=6750

Comment 1 Andreas Schneider 2020-12-09 12:37:50 UTC

We could get the service principal names from the keytab and then create new entries for each of them, however there is an issue with the kvno to get it right.

Comment 4 RHEL Program Management 2022-08-01 07:27:52 UTC

After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.

Comment 6 Pavel Filipensky 2022-08-02 08:43:09 UTC

Hi Andre,

thanks for spotting this. yes, this is a strech goal for Q3. I will reopen it.

Pavel

Comment 12 RHEL Program Management 2023-09-05 12:16:11 UTC

Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.

Comment 13 RHEL Program Management 2023-09-05 12:19:51 UTC

This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues.