Bug 1381901

Summary: Clarify using --server when installing an IPA client
Product: Red Hat Enterprise Linux 7 Reporter: Aneta Šteflová Petrová <apetrova>
Component: doc-Linux_Domain_Identity_Management_GuideAssignee: Aneta Šteflová Petrová <apetrova>
Status: CLOSED CURRENTRELEASE QA Contact: Namita Soman <nsoman>
Severity: unspecified Docs Contact:
Priority: medium    
Version: 7.2CC: rhel-docs
Target Milestone: rcKeywords: 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-02-03 08:24:53 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 Aneta Šteflová Petrová 2016-10-05 10:38:05 UTC 
Failures with discovery when using --server and trusts can be confusing. We were asked to clarify this.


Background (from email):

Question: What is the reasoning behind having ipa-client-install disable dns_lookup_realm and dns_lookup_kdc when the caller specifies the server?

Answer: --server is used to pin IPA client to a specific IPA server. This means
both SSSD and Kerberos library ensured to not try to access other
servers, both LDAP and KDC.

This predates FreeIPA's integration with Active Directory where we have
to do dynamic discovery of the users' AD domains and as result do
authentication against their domain controllers.

If you don't want to pin IPA client to a specific IPA server, you don't
need to use --server option. In RHEL 7.3 we have support for sites in
FreeIPA, which should work automatically by choosing closest server.

Alternatively, you can use configuration management tools to set
dns_lookup_realm and dns_lookup_kdc on the clients that need to be
pinned to a specific IPA server otherwise.
Comment 2 Aneta Šteflová Petrová 2017-02-03 08:24:53 UTC 
--server is now documented in 3.3.2. Installing a Client Non-interactively: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Linux_Domain_Identity_Authentication_and_Policy_Guide/client-install.html#client-install-non-interactive