-
-
Notifications
You must be signed in to change notification settings - Fork 994
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
EssentialsX XMPP SASL auth failed (TLS) #3962
Comments
EssentialsX XMPP by default should use TLS where available. Could you set |
Tried, and let's say that it wasn't very useful... It seems that EssentialsXMPP tries to check if it is running in an headless environment, but throws an exception because it can't access an Here's the full server log (I removed some things that I think are irrelevant, like some world loading info and dynmap stuff)
|
Hmm, apparently the XMPP library's debug mode is... a GUI? Either way, the message indicates that the connection was established, but the username/password combination you provided to EssentialsX was incorrect. TLS/STARTTLS and SASL PLAIN authentication are unrelated and both appear to be supported by You should double check that the username/password set on the server matches the username/password in your config. There's no indication that there's a bug in EssentialsX XMPP, and the XMPP module is largely unsupported, so there's not much we can do about this issue. |
The password is correct, I tried a lot of times with different accounts and XMPP servers. |
Could you try removing the After some testing, I can confirm that EssentialsX XMPP does in fact start a secure TLS connection before attempting to log in. When running XMPP on my machine with the debugger enabled, the debugger window's log shows the following response to authentication: <failure xmlns='urn:ietf:params:xml:ns:xmpp-sasl'><not-authorized/><text xml:lang='en'>Invalid username or password</text></failure> Unfortunately smack doesn't provide us with the proper "invalid username/password" message unless you use the graphical debugger, so we can't easily log authentication failures ourselves. After some trial and error, it appears the default XMPP I'll push a few changes to XMPP in a bit that should make the config a bit clearer and also require server-side TLS by default. |
Ok, I can confirm that removing the |
You should be able to run Going to close this issue as the main issue is resolved. If you have any further questions about how to use XMPP, feel free to ask a question on Discussions. |
Type of bug
Compatibility issue
/ess version
output[01:04:15 INFO]: Server version: 1.16.5-R0.1-SNAPSHOT git-Paper-449 (MC: 1.16.5)
[01:04:15 INFO]: EssentialsX version: 2.18.2.0
[01:04:15 INFO]: EssentialsXXMPP version: 2.18.2.0
[01:04:15 INFO]: Vault is not installed. Chat e permissions could not work.
[01:04:15 INFO]: You're using an unsupported server version!
(translated from Italian)
Server startup log
https://paste.gg/p/anonymous/89a17954de344a92a78ff39daa1a5967
EssentialsX config files
https://paste.gg/p/anonymous/ebbb71554bc54c3082038241cc4b1c7f
Error log (if applicable)
https://paste.gg/p/anonymous/529926294bd04dbfb8971038a4f6b005
Bug description
When tying to authenticate to the yourdata.forsale XMPP server I get an authentication error (
org.jivesoftware.smack.XMPPException: SASL authentication PLAIN failed: text
) even though the password is correct.Maybe yourdata.forsale only supports TLS/STARTTLS and EssentialsXXMPP doesn't?
Steps to reproduce
plugins/EssentialsXMPP/config.yml
Expected behaviour
The XMPP module should be able to login using SASL auth with START TLS
Actual behaviour
The XMPP module uses PLAIN authentication and throws an exception failing login
The text was updated successfully, but these errors were encountered: