Back to bug 1320838
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| RHEL Program Management | 2016-03-24 07:30:17 UTC | Keywords | FutureFeature | |
| Red Hat Bugzilla | 2016-03-24 07:30:17 UTC | Doc Type | Bug Fix | Enhancement |
| Petr Vobornik | 2016-03-24 19:12:26 UTC | Status | NEW | ASSIGNED |
| Brad Vaughan | 2016-03-24 20:26:27 UTC | CC | bvaughan | |
| Petr Vobornik | 2016-04-06 10:22:13 UTC | See Also | https://bugzilla.redhat.com/show_bug.cgi?id=1323316 | |
| Martin Kosek | 2016-06-10 12:33:51 UTC | Status | ASSIGNED | POST |
| Aneta Šteflová Petrová | 2016-06-27 10:55:26 UTC | Docs Contact | mmuehlfe | |
| Marc Muehlfeld | 2016-07-08 10:13:59 UTC | CC | mkosek | |
| Flags | needinfo?(mkosek) | |||
| Martin Kosek | 2016-07-08 10:25:54 UTC | Flags | needinfo?(mkosek) | |
| Marc Muehlfeld | 2016-07-11 12:14:53 UTC | Flags | needinfo?(mkosek) | |
| Marc Muehlfeld | 2016-07-21 07:03:08 UTC | CC | rhel-docs | |
| Component | ipa | doc-Linux_Domain_Identity_Management_Guide | ||
| Docs Contact | mmuehlfe | |||
| Assignee | ipa-maint | mmuehlfe | ||
| QA Contact | ksiddiqu | nsoman | ||
| Flags | needinfo?(mkosek) | |||
| RHEL Program Management | 2016-07-21 08:41:11 UTC | Keywords | Documentation | |
| Martin Kosek | 2016-07-21 11:51:45 UTC | Status | POST | MODIFIED |
| Component | doc-Linux_Domain_Identity_Management_Guide | ipa | ||
| Fixed In Version | ipa-4.4.0-2.1.el7 | |||
| Assignee | mmuehlfe | ipa-maint | ||
| QA Contact | nsoman | ksiddiqu | ||
| Ellen Newlands | 2016-07-21 12:40:47 UTC | CC | enewland | |
| Aneta Šteflová Petrová | 2016-08-05 06:49:32 UTC | Blocks | 1241714 | |
| Petr Spacek | 2016-08-09 12:48:52 UTC | CC | pspacek | |
| errata-xmlrpc | 2016-08-09 14:07:33 UTC | Status | MODIFIED | ON_QA |
| Marc Muehlfeld | 2016-08-12 10:49:03 UTC | CC | abokovoy, mmuehlfe | |
| Doc Text | IdM enables users to access clients using an AD DNS host name Identity Management (IdM) now enables users in a trusted environment with Active Directory (AD) to access clients using their AD host name. 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. | |||
| Flags | needinfo?(abokovoy) | |||
| Marc Muehlfeld | 2016-08-12 12:32:46 UTC | Doc Text | IdM enables users to access clients using an AD DNS host name Identity Management (IdM) now enables users in a trusted environment with Active Directory (AD) to access clients using their AD host name. 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. | 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. |
| Flags | needinfo?(abokovoy) | |||
| Marc Muehlfeld | 2016-08-12 12:36:35 UTC | Docs Contact | mmuehlfe | |
| Doc Type | Enhancement | Release Note | ||
| Aneta Šteflová Petrová | 2016-08-19 07:35:38 UTC | 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. | 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-Beta/html/Windows_Integration_Guide/ipa-in-ad-dns.html. |
| Varun Mylaraiah | 2016-09-13 12:19:48 UTC | Status | ON_QA | VERIFIED |
| CC | mvarun | |||
| Assignee | ipa-maint | mvarun | ||
| Marc Muehlfeld | 2016-10-07 08:40:33 UTC | Docs Contact | mmuehlfe | |
| Marc Muehlfeld | 2016-10-17 09:29:51 UTC | 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-Beta/html/Windows_Integration_Guide/ipa-in-ad-dns.html. | 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. |
| Lenka Špačková | 2016-10-17 14:23:42 UTC | Docs Contact | mmuehlfe | |
| errata-xmlrpc | 2016-11-02 14:57:06 UTC | Status | VERIFIED | RELEASE_PENDING |
| errata-xmlrpc | 2016-11-04 05:52:36 UTC | Status | RELEASE_PENDING | CLOSED |
| Resolution | --- | ERRATA | ||
| Last Closed | 2016-11-04 01:52:36 UTC |
Back to bug 1320838