Bug 1390994

Summary:	Documentation lacks Kerberos over http description
Product:	Red Hat Enterprise Linux 7	Reporter:	Oleg Fayans <ofayans>
Component:	doc-System_Level_Authentication_Guide	Assignee:	Aneta Šteflová Petrová <apetrova>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Kaushik Banerjee <kbanerje>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	7.4	CC:	amarecek, cheimes, jhrozek, 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:	2017-03-14 09:35:52 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:

Description Oleg Fayans 2016-11-02 11:34:35 UTC

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

Comment 1 Aneta Šteflová Petrová 2016-11-02 12:11:33 UTC

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?

Comment 4 Oleg Fayans 2016-11-07 14:55:52 UTC

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

Comment 5 Aneta Šteflová Petrová 2016-11-08 11:57:41 UTC

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

Comment 15 Aneta Šteflová Petrová 2017-03-14 09:35:52 UTC

The update is now available on the Customer Portal.