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 1400618 - Document when and why does Kerberos authentication use UDP and when does it use TCP
Summary: Document when and why does Kerberos authentication use UDP and when does it u...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: doc-Windows_Integration_Guide
Version: 7.4
Hardware: Unspecified
OS: Unspecified
medium
unspecified
Target Milestone: rc
: ---
Assignee: Marc Muehlfeld
QA Contact: Kaushik Banerjee
URL:
Whiteboard:
Depends On:
Blocks: 1566354
TreeView+ depends on / blocked
 
Reported: 2016-12-01 16:00 UTC by Jakub Hrozek
Modified: 2019-04-09 10:31 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-04-09 10:31:38 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

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.
Note You need to log in before you can comment on or make changes to this bug.