Hide Forgot
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.