-
Notifications
You must be signed in to change notification settings - Fork 371
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Wrong SASL mechanism is used after upgrade 0.5.2 -> 0.7.0 #637
Comments
DaveLomber
changed the title
Wrong SASL mechanism is used
Wrong SASL mechanism is used after upgrade 0.5.2 -> 0.7.0
Apr 7, 2019
As I see it somehow touched here 18984f7 |
@sonnyp could you provide your feedback here |
@DaveLomber thanks for looking into it I wrongly assumed that a domain would not offer both anonymous and non anonymous mechanisms. I will address this. |
Hi @sonnyp |
fixed in #691 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I used 0.5.2 version and all was good. I use PLAIN SASL mechanism to authenticate
Now I upgraded to 0.7.0 and my code is broken, by some reason the lib started choosing ANONYMOUS mechanism even if I provide the username & password
I did some debugging of this file https://github.com/xmppjs/xmpp.js/blob/master/packages/sasl/index.js#L80
and here is what I got:
so we got here
intersection= ["ANONYMOUS", "PLAIN"]
and thenlet mech = intersection[0]
and we gotANONYMOUS
Any reason for this? can we somehow set a mechanism we want to use?
The text was updated successfully, but these errors were encountered: