Spark v 2.7.6 won't accept correct credentials

Since updating Spark to version 2.7.6, users credentials are no longer accepted. I had to roll back to the previous version before users could log in again. Our server is using Openfire 3.7.0 and I know an update is available. Is it required to get Spark 2.7.6 to work properly or is there a bug in 2.7.6?

2.7.6 works fine on my test Openfire 4.0.2 and production 4.0.1 (200 users) servers. Can’t test against such an old version like 3.7.0, so not sure what can be causing this. If you say that 2.7.5 is working, then maybe it’s JNA or Libjitsi libraries update, though very unlikely. But that’s the only somewhat major updates in 2.7.6. No ground braking changes (most of them for Mac OS X actually).

Maybe there are some logs in the Spark and Openfire errors log. Spark’s is in the user profile in AppData\Roaming\Spark. Openfire’s in Openfire/logs.

The Spark logs did show the following:

Mar 22, 2016 9:44:42 AM org.jivesoftware.spark.util.log.Log error

SEVERE:

java.io.FileNotFoundException: C:\Users\dtrujillo\AppData\Roaming\Spark\user\dtrujillo@wmgu-files01\transcript s\taco tuesdays, where’s the salsa?@conference.wmgu-files01_current.xml (The filename, directory name, or volume label syntax is incorrect)

at java.io.FileOutputStream.open(Native Method)

at java.io.FileOutputStream.(Unknown Source)

at java.io.FileOutputStream.(Unknown Source)

at org.jivesoftware.sparkimpl.plugin.transcripts.ChatTranscripts.writeToFile(ChatT ranscripts.java:120)

at org.jivesoftware.sparkimpl.plugin.transcripts.ChatTranscripts.appendToTranscrip t(ChatTranscripts.java:83)

at org.jivesoftware.sparkimpl.plugin.transcripts.ChatTranscriptPlugin.persistChatR oom(ChatTranscriptPlugin.java:243)

at org.jivesoftware.spark.ui.ChatRoom.checkForEnter(ChatRoom.java:702)

at org.jivesoftware.spark.ui.ChatRoom.access$300(ChatRoom.java:90)

at org.jivesoftware.spark.ui.ChatRoom$3.keyPressed(ChatRoom.java:335)

at java.awt.Component.processKeyEvent(Unknown Source)

at javax.swing.JComponent.processKeyEvent(Unknown Source)

at java.awt.Component.processEvent(Unknown Source)

at java.awt.Container.processEvent(Unknown Source)

at java.awt.Component.dispatchEventImpl(Unknown Source)

at java.awt.Container.dispatchEventImpl(Unknown Source)

at java.awt.Component.dispatchEvent(Unknown Source)

at java.awt.KeyboardFocusManager.redispatchEvent(Unknown Source)

at java.awt.DefaultKeyboardFocusManager.dispatchKeyEvent(Unknown Source)

at java.awt.DefaultKeyboardFocusManager.preDispatchKeyEvent(Unknown Source)

at java.awt.DefaultKeyboardFocusManager.typeAheadAssertions(Unknown Source)

at java.awt.DefaultKeyboardFocusManager.dispatchEvent(Unknown Source)

at java.awt.Component.dispatchEventImpl(Unknown Source)

at java.awt.Container.dispatchEventImpl(Unknown Source)

at java.awt.Window.dispatchEventImpl(Unknown Source)

at java.awt.Component.dispatchEvent(Unknown Source)

at java.awt.EventQueue.dispatchEventImpl(Unknown Source)

at java.awt.EventQueue.access$300(Unknown Source)

at java.awt.EventQueue$3.run(Unknown Source)

at java.awt.EventQueue$3.run(Unknown Source)

at java.security.AccessController.doPrivileged(Native Method)

at java.security.ProtectionDomain$1.doIntersectionPrivilege(Unknown Source)

at java.security.ProtectionDomain$1.doIntersectionPrivilege(Unknown Source)

at java.awt.EventQueue$4.run(Unknown Source)

at java.awt.EventQueue$4.run(Unknown Source)

at java.security.AccessController.doPrivileged(Native Method)

at java.security.ProtectionDomain$1.doIntersectionPrivilege(Unknown Source)

at java.awt.EventQueue.dispatchEvent(Unknown Source)

at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source)

at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source)

at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)

at java.awt.EventDispatchThread.pumpEvents(Unknown Source)

at java.awt.EventDispatchThread.pumpEvents(Unknown Source)

at java.awt.EventDispatchThread.run(Unknown Source)

The error seems to be related to a group chat transcript. You can try looking for that xml file and maybe delete it. You can also try renaming your Spark profile in AppData\Roaming and try with a fresh one.

We have the same issue here too after upgrading from 2.7.3 to 2.7.6…

Which logs should I post?, as I didn’t see too much in my logs in my roaming profile…

What Openfire version are you using, Ryan?

If you don’t see anything in C:\Users\user\AppData\Roaming\Spark\logs\errors.log, then you can try Openfire’s errors log for anything seemingly related to failed login.

Unsure actually. Is there a way to tell via spark? I don’t have access to the openfire server as far as I know…

No, there is no way to tell it from Spark.

I think it might be JNA library update (which stands for Java Native Access). My theory is that older Openfire is using Java 7 (some old version) and Spark is using Java 8 and there is probably some incompatibility. @speedy ?

jna shouldn’t be the issue…I’m at a loss. If I had to have a guess, I’m willing to say something didn’t update or install correctly. I’m with you…if it was working with 2.7.5, it should work fine.

I’d prob just make of backup of %appdata%\Spark

and

uninstall Spark

delete c:\program files (x86)\Spark

deleted %appdata%\Spark

reinstall

to be fair I upgraded from v2.7.3.

I can try 2.7.5 if you have an installer available? and see how that goes.

We just got a company wide broadcast to not install the latest, so I assume the server guys are also trying to figure it out.

www.igniterealtime.org/downloads/download-landing.jsp?file=spark/spark_2_7_5.exe

You can just replace version number in the link and download 2.7.5 or 2.7.4.

oh good to know!

2.7.5 bld752 downloaded, and is installed/up and running (connected to the server just fine)!

just 2.7.6 wont connect to the server…

I could try the profile idea next… but i’ve installed a few different versions overtop one another today, and the only one with issue is the .6

ok I have tried this method, removed roaming and program files.

And instaled 2.7.6, same issue: “Invalid username or password”.

I do notice that there is a considerable filesize difference to the installers:

spark_2_7_5.exe = 60,158kb

spark_2_7_6.exe = 72,464 kb

I see this in the warn.log:

Mar 23, 2016 1:31:23 PM org.jivesoftware.spark.util.log.Log warning

WARNING: Exception in Login:

No response from the server.:

at org.jivesoftware.smack.NonSASLAuthentication.authenticate(NonSASLAuthentication .java:73)

at org.jivesoftware.smack.SASLAuthentication.authenticate(SASLAuthentication.java: 357)

at org.jivesoftware.smack.XMPPConnection.login(XMPPConnection.java:243)

at org.jivesoftware.LoginDialog$LoginPanel.login(LoginDialog.java:1105)

at org.jivesoftware.LoginDialog$LoginPanel.access$1400(LoginDialog.java:333)

at org.jivesoftware.LoginDialog$LoginPanel$4.construct(LoginDialog.java:867)

at org.jivesoftware.spark.util.SwingWorker$2.run(SwingWorker.java:141)

at java.lang.Thread.run(Unknown Source)

Mar 23, 2016 1:32:44 PM org.jivesoftware.spark.util.log.Log warning

WARNING: Exception in Login:

No response from the server.:

at org.jivesoftware.smack.NonSASLAuthentication.authenticate(NonSASLAuthentication .java:73)

at org.jivesoftware.smack.SASLAuthentication.authenticate(SASLAuthentication.java: 357)

at org.jivesoftware.smack.XMPPConnection.login(XMPPConnection.java:243)

at org.jivesoftware.LoginDialog$LoginPanel.login(LoginDialog.java:1105)

at org.jivesoftware.LoginDialog$LoginPanel.access$1400(LoginDialog.java:333)

at org.jivesoftware.LoginDialog$LoginPanel$4.construct(LoginDialog.java:867)

at org.jivesoftware.spark.util.SwingWorker$2.run(SwingWorker.java:141)

at java.lang.Thread.run(Unknown Source)

I’m experiencing the same issue rzah. Users have always updated their version of Spark when a new update becomes available. No version has ever had trouble connecting to the server prior to v. 2.7.6. I also told all users not to update right now. I suppose I can wait for 2.7.7 and see if it works. Don’t mind leapfrogging this version and moving on. However, if a bug is discovered and fixed, I’d like to learn what it is.

can you see if there is any output in c:\program~\Spark\logs

sorry to say, but it’s empty.

fyi fwiw: I just reinstalled 2.7.5 over top of that non functioning 2.7.6 and i’m alive again…

I’m unable to reproduce the issue.

I just installed Openfire 3.7.0 (running java 6 btw!), and I’m able to connect just fine with 2.7.6

The size increase is due to Libjitsi patch which added a lot of new libraries to the install. Also install4j has been updated on install producing system, so it could affect the size also.