RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1873567 - Document Channel Binding related fixes
Summary: Document Channel Binding related fixes
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: doc-Release_Notes-8-en-US
Version: ---
Hardware: Unspecified
OS: Unspecified
medium
unspecified
Target Milestone: rc
: 8.3
Assignee: Lucie Vařáková
QA Contact: RHEL DPM
Filip Hanzelka
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-08-28 15:56 UTC by Filip Hanzelka
Modified: 2020-10-09 16:41 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
.Adjusting to new Microsoft LDAP channel binding and LDAP signing requirements With recent Microsoft updates, Active Directory (AD) flags the clients that do not use the default Windows settings for LDAP channel binding and LDAP signing. As a consequence, RHEL systems that use the System Security Services Daemon (SSSD) for direct or indirect integration with AD might trigger error Event IDs in AD upon successful Simple Authentication and Security Layer (SASL) operations that use the Generic Security Services Application Program Interface (GSSAPI). To prevent these notifications, configure client applications to use the Simple and Protected GSSAPI Negotiation Mechanism (GSS-SPNEGO) SASL mechanism instead of GSSAPI. To configure SSSD, set the `ldap_sasl_mech` option to `GSS-SPNEGO`. Additionally, if channel binding is enforced on the AD side, configure any systems that use SASL with SSL/TLS in the following way: . Install the latest versions of the `cyrus-sasl`, `openldap` and `krb5-libs` packages that are shipped with RHEL 8.3 and later. . In the `/etc/openldap/ldap.conf` file, specify the correct channel binding type by setting the `SASL_CBINDING` option to `tls-endpoint`. For more information, see link:https://access.redhat.com/articles/4661861[Impact of Microsoft Security Advisory ADV190023 | LDAP Channel Binding and LDAP Signing on RHEL and AD integration].
Clone Of:
Environment:
Last Closed: 2020-09-15 15:27:29 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Filip Hanzelka 2020-08-28 15:56:24 UTC 
MArtin Kosek: "I do not see release notes for the Channel Binding related fixes (in cyrus-sasl, krb5, openldap) and how it works with the MSFT server setting for CB (details can be referred to the respective article that THorsten collates)"
Comment 7 Filip Hanzelka 2020-09-15 15:27:29 UTC 
Published: https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8-beta/html-single/8.3_release_notes/index
Note You need to log in before you can comment on or make changes to this bug.