Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

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:

As of version 4.2 IPA provides an http proxy for it's Kerberos server functionality. This means that if the client has only access to server's port 80 (i. e., Kerberos' port 88 is unreachable from the client machine), client can still kinit, provided that it's krb5 client is configured to use https://<server_hostname>/KdcProxy as kdc (and sssd is restarted afterwards).

See this design page for details:
http://www.freeipa.org/page/V4/KDC_Proxy
 

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

Thanks for the bug report, Oleg.

We have some docs for KDC proxy here: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/System-Level_Authentication_Guide/Configuring_a_Kerberos_5_Server.html#KKDCP
I'd like to figure out how to update this section to fix this bug:

* Do you see your report as another use case that we should add to the existing KDC Proxy section?
* Is the existing section okay, but missing the step to restart SSSD?
* Or is there something else you'd like us to do?

The document listed above describes rather how to enable/disable this feature on master, It should include the description of how to configure the client to use it:
1. Update /etc/krb5.conf on the client
2. Restart sssd on client

I made a few updates to the section, notably:

* Added a few titles to distinguish the different parts of the section (configuring, verifying, disabling) -- this will help to clearly distinguish the client configuration steps from the other content
* Added the missing step to restart SSSD

The update is now available on the Customer Portal.