When I removed the cached password from the spark.propterties file, my SSO is very broken. Which is to say, I don’t think it is really working at all.
Still get 401 errors.
Updated openfire to 3.6.4 this morning. Cleared out logs on server and my machine.
Logon attempt is barely noticed in the server logs, only reporting in the debug log:
2009.05.04 08:21:13 000776 (01/05/00) - Connection #5 tested: OK
2009.05.04 08:21:13 000777 (01/05/00) - Connection #5 tested: OK
Locally, my spark debug log provides a litte more information:
May 4, 2009 8:21:13 AM org.jivesoftware.spark.util.log.Log warning
WARNING: Exception in Login:
at org.jivesoftware.smack.NonSASLAuthentication.authenticate(NonSASLAuthentication .java:94)
at org.jivesoftware.smack.SASLAuthentication.authenticate(SASLAuthentication.java: 227)
at java.lang.Thread.run(Unknown Source)
This is pretty much where I’ve been for a week or so. This is also where I am confused about ‘Single’ sign-on vs. ‘No’ sign-on. That is, if I give my client a chance to cache the password - then change my password on the server…logon and off my machine…I do not have to update Spark. But I have not been able to logon with the SSO checkbox checked - without providing at least 1 valid logon attempt to Spark. Otherwise, it’s all about the 401 error above.
I’d love to figure this one out. Thanks for any help anyone can provide.