Bug 1320838
| Summary: | [RFE] Support IdM Client in a DNS domain controlled by AD | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Martin Kosek <mkosek> | ||||
| Component: | ipa | Assignee: | Varun Mylaraiah <mvarun> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Kaleem <ksiddiqu> | ||||
| Severity: | unspecified | Docs Contact: | Marc Muehlfeld <mmuehlfe> | ||||
| Priority: | unspecified | ||||||
| Version: | 7.3 | CC: | abokovoy, bvaughan, enewland, mkosek, mmuehlfe, mvarun, pspacek, pvoborni, rcritten, rhel-docs | ||||
| Target Milestone: | rc | Keywords: | Documentation, FutureFeature | ||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | ipa-4.4.0-2.1.el7 | Doc Type: | Release Note | ||||
| Doc Text: |
Documentation now describes configuration and limitations of IdM clients using an AD DNS host name
The Identity Management (IdM) documentation has been enhanced and now describes the configuration of IdM clients located in the DNS name space of a trusted Active Directory (AD) domain. Note that this is not a recommended configuration and has some limitations. For example, only password authentication is available to access these clients instead of single sign-on. Red Hat recommends to always deploy IdM clients in a DNS zone different from the ones owned by AD and access IdM clients through their IdM host names.
For detailed information, see https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Windows_Integration_Guide/ipa-in-ad-dns.html.
|
Story Points: | --- | ||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2016-11-04 05:52:36 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: | |||||
| Embargoed: | |||||||
| Bug Depends On: | |||||||
| Bug Blocks: | 1241714 | ||||||
| Attachments: |
|
||||||
|
Description
Martin Kosek
2016-03-24 07:14:24 UTC
Upstream ticket: https://fedorahosted.org/freeipa/ticket/5762 Upstream ticket: https://fedorahosted.org/freeipa/ticket/5903 The current recipe on joining clients from Windows controlled domain in FreeIPA/IdM domain is described in this article: http://www.freeipa.org/page/V4/IPA_Client_in_Active_Directory_DNS_domain Ticket #5903 was fixed upstream: https://fedorahosted.org/freeipa/changeset/f0160a2ed28325e46be2921ac44d71ee88d1b3b1/ can we switch component to LDI guide given that there is no code? (https://fedorahosted.org/freeipa/ticket/5903 was just a convenient helper) I changed the component of the BZ and removed it from the RN list. (In reply to Petr Vobornik from comment #11) > can we switch component to LDI guide given that there is no code? > (https://fedorahosted.org/freeipa/ticket/5903 was just a convenient helper) I do not think we should do that. There is #5903 always add mapping (my hostname) = (IPA realm) to krb5.conf that can be tested that you mentioned. I would like to use this Bugzilla as explicit exclamation of support levels of these scenarios, as described in the new documentation. At minimum, the Bugzilla can be used for tracking test coverage and automation. This setup is dicussed at length in following blog post: http://rhelblog.redhat.com/2016/07/13/i-really-cant-rename-my-hosts/ Created attachment 1200480 [details]
Scenarios_for_Frankenstein_RFE
Verified
ipa-server-4.4.0-10.el7.x86_64
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://rhn.redhat.com/errata/RHBA-2016-2404.html |