Bug 1193425
| Summary: | A broker configured with disabled authentication requires authentication from a client connected from Windows | |||
|---|---|---|---|---|
| Product: | Red Hat Enterprise MRG | Reporter: | Petra Svobodová <psvobodo> | |
| Component: | Release_Notes | Assignee: | Nobody <nobody> | |
| Status: | CLOSED UPSTREAM | QA Contact: | MRG Quality Engineering <mrgqe-bugs> | |
| Severity: | high | Docs Contact: | ||
| Priority: | unspecified | |||
| Version: | Development | CC: | jross, messaging-bugs, messaging-qe-bugs, zkraus | |
| Target Milestone: | 3.0.2 | Keywords: | Regression, TestBlocker | |
| Target Release: | --- | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | Doc Type: | Bug Fix | ||
| Doc Text: |
Because of changes in the included security fixes, starting with this release Windows client programs that use the default PLAIN authentication may now fail if authentication is turned off on the broker, where before they erroneously succeeded.
To work around this, explicitly use ANONYMOUS by using `--connection-options '{sasl_mechanisms:ANONYMOUS}'` or you can use a valid username (to work with the default PLAIN mechanism if you have it set up). For example, with valid user 'jsmith', it would be `--connection-options '{username:jsmith}'`
|
Story Points: | --- | |
| Clone Of: | 1192924 | |||
| : | 1197134 1201741 (view as bug list) | Environment: | ||
| Last Closed: | 2025-02-10 03:44:04 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: | 1195163, 1197134, 1201741 | |||
|
Comment 3
Irina Boverman
2015-02-26 19:21:57 UTC
I have changed the group membership from Red Hat only to Public, and made all comments private so this will appear in the release notes. *** Bug 1201741 has been marked as a duplicate of this bug. *** This product has been discontinued or is no longer tracked in Red Hat Bugzilla. |