Strange mistake

Strange mistake. With spark 2.x beta I could connect using wildfire integration with custom database, but now with 2.0 spark release I cannot connect. In the logs of wildfire there are no errors but in logs of spark there are mistakes:

SASL authentication failed:

(SwingWorker.java:132)

at java.lang.Thread.run(Unknown Source)*at org.jivesoftware.smack.SASLAuthentication.authenticate(SASLAuthentication.java: 204)

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

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

at org.jivesoftware.LoginDialog$LoginPanel.access$400(LoginDialog.java:164)

at org.jivesoftware.LoginDialog$LoginPanel$1.construct(LoginDialog.java:486)

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

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

logs of spark 2-03 beta

at org.jivesoftware.smack.SASLAuthentication.bindResourceAndEstablishSession(SASLA uthentication.java:306)

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

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

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

at org.jivesoftware.LoginDialog$LoginPanel.access$400(LoginDialog.java:163)

at org.jivesoftware.LoginDialog$LoginPanel$1.construct(LoginDialog.java:485)

at org.jivesoftware.spark.util.SwingWorker$2.run

Error.log of wildfire:

2006.09.09 15:36:56 org.jivesoftware.wildfire.handler.IQHandler.process(IQHandler.java:68) Internal server error

java.lang.IllegalArgumentException: Illegal JID: myuser@mydomain.com@23.158.57.125/spark

at org.xmpp.packet.JID.init(JID.java:401)

at org.xmpp.packet.JID.<init>(JID.java:272)

at org.jivesoftware.wildfire.ClientSession.setAuthToken(ClientSession.java:521)

at org.jivesoftware.wildfire.handler.IQBindHandler.handleIQ(IQBindHandler.java:127 )

at org.jivesoftware.wildfire.handler.IQHandler.process(IQHandler.java:48)

at org.jivesoftware.wildfire.IQRouter.handle(IQRouter.java:268)

at org.jivesoftware.wildfire.IQRouter.route(IQRouter.java:96)

at org.jivesoftware.wildfire.spi.PacketRouterImpl.route(PacketRouterImpl.java:67)

at org.jivesoftware.wildfire.net.SocketReader.processIQ(SocketReader.java:250)

at org.jivesoftware.wildfire.net.ClientSocketReader.processIQ(ClientSocketReader.j ava:51)

at org.jivesoftware.wildfire.net.SocketReader.process(SocketReader.java:216)

at org.jivesoftware.wildfire.net.BlockingReadingMode.readStream(BlockingReadingMod e.java:156)

at org.jivesoftware.wildfire.net.BlockingReadingMode.run(BlockingReadingMode.java: 62)

at org.jivesoftware.wildfire.net.SocketReader.run(SocketReader.java:123)

at java.lang.Thread.run(Thread.java:595)

Caused by: org.jivesoftware.stringprep.StringprepException: Contains prohibited code points.

at org.jivesoftware.stringprep.Stringprep.nodeprep(Stringprep.java:120)

at org.xmpp.packet.JID.init(JID.java:350)

… 14 more

Message was edited by: urgido

Hi Urgido,

In spark, are you specifying the user exactly as myuser@mydomain.com? Or are you using just “myuser”.

Thanks.

Derek

I test it with that two ways

Hi,

"myuser@mydomain.com@ip-address/spark" looks really weird. Is it possible that Wildfire tries to use the email address column instead of the username column of your remote database?

Is it still running fine with Spark 114?

LG

actually, I use the column of email because i use the identification of my clients using his/her email. Well I edit wildfire.xml and now don’'t work the integration LOL! I have +500 green white hairs

mmhhhLpppfOfffLff,

how many green white hairs do you have?

Does it work now or does it not work, “don’'t” usually means does not.

LG

hehehe if you can I can give you a pass of my dedicated server by pm

Hi,

I did never try the database auth provider, so it may help to post the error messages / error.log - I wonder if you still see the same error.

And I wonder whether Spark 114 runs fine.

LG

the error of spark and wildfire or which?

Hi Urigdo,

One of the things that has been added to Spark, was the escaping of JID’'s in the product. I would love to test this feature out more on your system if you would allow for it. Send me a private message if you could give me permission.

Cheers,

Derek

I think the solution is easy but I cannot idea How I can solved check this error:

java.lang.IllegalArgumentException: Illegal JID: urgido@domains.com@my.ip.here

So I need to agree the @ on JID’‘S for work’'s that. Regards

How I can make “hide” the text input of “server jabber name”?

Regards