[Spark 3.0.2] Very long error window

Spark
1

Hello.

I installed the 3.0.2 version. I transfer the configuration file to workstations via batch.
I thought about adding a user login to it. This resulted in a very long error window.

error_long
error_long3607×122 49.2 KB

org.jivesoftware.smack.SmackException$SmackSaslException: No supported and enabled SASL Mechanism provided by server. Server announced mechanisms: [PLAIN]. Registered SASL mechanisms with Smack: [SASL Mech: SCRAM-SHA-1-PLUS, Prio: 100, SASL Mech: SCRAM-SHA-1, Prio: 110, SASL Mech: DIGEST-MD5, Prio: 200, SASL Mech: CRAM-MD5, Prio: 300, SASL Mech: PLAIN, Prio: 400, SASL Mech: X-OAUTH2, Prio: 410, SASL Mech: EXTERNAL, Prio: 500, SASL Mech: ANONYMOUS, Prio: 500, SASL Mech: EXTERNAL, Prio: 500]. Enabled SASL mechanisms for this connection: null. Blacklisted SASL mechanisms: [SCRAM-SHA-1-PLUS]. Skip reasons: [Skipping SASL Mech: PLAIN, Prio: 400 because a password is required for it, but none was provided to the connection configuration]
	at org.jivesoftware.smack.SASLAuthentication.selectMechanism(SASLAuthentication.java:366)
	at org.jivesoftware.smack.SASLAuthentication.authenticate(SASLAuthentication.java:188)
	at org.jivesoftware.smack.AbstractXMPPConnection.authenticate(AbstractXMPPConnection.java:897)
	at org.jivesoftware.smack.tcp.XMPPTCPConnection.loginInternal(XMPPTCPConnection.java:382)
	at org.jivesoftware.smack.AbstractXMPPConnection.login(AbstractXMPPConnection.java:638)
	at org.jivesoftware.gui.LoginUIPanel.login(LoginUIPanel.java:1273)
	at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
	at java.util.concurrent.FutureTask.run(Unknown Source)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
	at java.lang.Thread.run(Unknown Source)

If there is no user and I run Spark, a short message about an invalid login or password will appear. But if I run Spark only with a login, without a password, such a long error message is generated.

And from the configuration file:
ssoMethod=file
saslGssapiSmack3compat=false

2

Hello, I would like to know if you were able to resolve this issue. I am experiencing the same error and I’m not sure what might be happening.

3

Hi @Lucas_Augusto_de_Sou

Sorry for answering so late - I missed your question.
I can’t remember seeing this message recently, but I haven’t checked it thoroughly either, so maybe no one is just informing me about it.

I’ve also changed a bit about myself since then. I am currently trying to upload the configuration file using GPO.

It seems to me that the reported problem should be solved by the developers themselves by adding appropriate line breaks in the message. For me, the lack of such protection allowing the generation of such long windows is a bug.
A solution on our part may be to not pass this login in the configuration file. Let the user enter the login themselves.