Bug 1400618

Summary:	Document when and why does Kerberos authentication use UDP and when does it use TCP
Product:	Red Hat Enterprise Linux 7	Reporter:	Jakub Hrozek <jhrozek>
Component:	doc-Windows_Integration_Guide	Assignee:	Marc Muehlfeld <mmuehlfe>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Kaushik Banerjee <kbanerje>
Severity:	unspecified	Docs Contact:
Priority:	medium
Version:	7.4	CC:	fhanzelk, jhrozek, rharwood, rhel-docs
Target Milestone:	rc	Keywords:	Documentation
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-04-09 10:31:38 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Bug Depends On:
Bug Blocks:	1566354

Description Jakub Hrozek 2016-12-01 16:00:24 UTC

Description of problem:
When SSSD is authenticating an AD user, it calls out to libkrb5. Normally, the Kerberos protocol uses UDP with optional fail over to TCP in case the data from the KDC would be too big. However, in AD environments, the fail over happens pretty much all the time, because AD also attaches a PAC to the Kerberos tickets. The PAC contains authorization data, including all the SIDs of groups the user is a member of which makes it usually too big for UDP.

The reason this should be documented is that at the moment, SSSD enrolled to AD always uses UDP but falls back to TCP pretty much always which might be confusing. In the future (please see bug #1399262) we are considering defalting to TCP in the first place, because the switch to TCP would happen anyway.

I think our books alrady document that both UDP and TCP ports should be open, but it might be nice to say why this is needed. If we extend the books for the 7.4 release, it would be nice to check if the TCP-by-default (tracked in #1399262) was also implemented and document that at least for user authentication TCP is used by default.


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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 8 Marc Muehlfeld 2019-04-09 10:31:38 UTC

The update is now available on the Customer Portal.