Type |
Task
|
Priority |
Normal
|
Assignee | |
Version |
none
|
Sprints |
n/a
|
Customer |
n/a
|
Issue Votes (0)
Type |
Task
|
Priority |
Normal
|
Assignee | |
Version |
none
|
Sprints |
n/a
|
Customer |
n/a
|
When Halcyon detects support for SASL2 it tries to use it. However, at the same time it tries to use SASL1 on the features change as SASL2 is not completed yet (is in progress). That should be blocked, and if SASL2 is started then SASL1 shouldn't try to authenticate.