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.

Description of problem:

kdcproxy seems to use UDP by default.
UDP might not be the best choice to encapsulate large payloads.
Also some network firewalls might also be configured to drop UDP packets with sizeof(payload) > 500 bytes or so.

As the use-case for kdcproxy on IDM hosts is a DMZ, it sounds reasonable to optimize network traffic coming from kdcproxy for firewalls.

RFE: 
* either:
** make sure to automatically switch to TCP if payload size is over 500 bytes
  Or:
** use TCP by default
 and:
* log a warning when only UDP URLs are provided for the servers to be contacted


Version-Release number of selected component (if applicable):
python-kdcproxy-0.4.1-1.fc30

Verified Using Version :
python3-kdcproxy-0.4-5.module+el8.2.0+4691+a05b2456.noarch
ipa-server : version: 4.8.4 release: 4.module+el8.2.0+5591+1f878b19

As this needs sanity only verification.
Adding results of downstream:pytest::kdcproxy

2020-02-14T21:00:19+0000 ---------- generated xml file: /home/jenkins/tews/kdcproxy/junit.xml -----------
2020-02-14T21:00:19+0000 ----- generated html file: file:///home/jenkins/tews/kdcproxy/report.html ------
2020-02-14T21:00:19+0000 [32m[1m========================= 11 passed in 1146.07 seconds =========================[0m
2020-02-14T21:00:19+0000 RETURN CODE: 0
2020-02-14T21:00:19+0000 UPSTREAM TESTS STEP END: src/kdcproxy
2020-02-14T21:00:19+0000 PHASE END: test

Based on this marking bz as verified.

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, 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/RHEA-2020:1640