Bug 1421663
Summary: | support proper SASL GSS-SPNEGO in CyrusSASL | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Alexander Bokovoy <abokovoy> |
Component: | cyrus-sasl | Assignee: | Jakub Jelen <jjelen> |
Status: | CLOSED ERRATA | QA Contact: | Namita Soman <nsoman> |
Severity: | unspecified | Docs Contact: | Mirek Jahoda <mjahoda> |
Priority: | unspecified | ||
Version: | 7.4 | CC: | mkosek, nsoman, pasik, pkis, pvrabec |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | cyrus-sasl-2.1.26-21 | Doc Type: | Bug Fix |
Doc Text: |
SPNEGO in Cyrus SASL is now compatible with Microsoft Windows
Prior to this update, the Red Hat Enterprise Linux implementation of Simple and Protected GSSAPI Negotiation Mechanism (SPNEGO) in Cyrus Simple Authentication and Security Layer (SASL) was not compatible with the Microsoft Windows counterpart. As a consequence, the Red Hat Enterprise Linux tools using the _cyrus-sasl_ packages were not able to use SPNEGO when attempting to connect to Windows services. These tools were also not able to accept connections from Windows clients. The _cyrus-sasl_ packages have been fixed, and SPNEGO in the Red Hat Enterprise Linux Cyrus SASL version is now compatible with the Microsoft Windows counterpart.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2017-08-01 20:56:22 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: | 1181853, 1345975 |
Description
Alexander Bokovoy
2017-02-13 11:54:36 UTC
For the record, the pull request was submitted upstream by Simo and is now merged into the master: https://github.com/cyrusimap/cyrus-sasl/pull/424 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://access.redhat.com/errata/RHBA-2017:2034 |