Wow, seems like you hunted that down and killed it and they aren't applying anything and taking the patches in yet. Heck one of their bugs is 4 years old and they don't seem to be in a hurry.
Is there a way to remove SASL Digest MD5 layer on openfire in sipx to test spark 2.6.3 against? I am guessing I have to edit the sasl.mechs to not use DIGEST-MD5, but I don't see a straightforward way to get these into the openfire.xml because it looks like there are several of these files and the syntax doesnt match the DOCS at ingniterealtime.org. Are these values being written from a database instead? Is this an edit in postgres instead? On Sat, Jan 28, 2012 at 7:56 AM, Mircea Carasel <[email protected]> wrote: > >> SASLAuthentication.java is brought in or not? >> >> http://codingteam.net/project/jappix/forum/show/4379 >> >> Does anyone have an opinion on this? >> >> On Fri, Jan 27, 2012 at 2:56 PM, Tony Graziano >> <[email protected]> wrote: >> > I have a new system using its own domain and the hostname is NOT the >> > sipdomain name. >> > >> > After comparing a spark login (debug log)--- >> > >> > 2012.01.27 14:25:08 execute: -> >> > 2012.01.27 14:25:08 execute: Request performed successfully >> > 2012.01.27 14:25:08 execute: <- >> > 2012.01.27 14:25:13 NIOConnection: startTLS: using c2s >> > 2012.01.27 14:25:14 SASLAuthentication: SaslException >> > javax.security.sasl.SaslException: DIGEST-MD5: digest response format >> > violation. Nonexistent realm: voice.myitdepartment.net >> > at >> > com.sun.security.sasl.digest.DigestMD5Server.validateClientResponse(DigestMD5Server.java:430) >> > at >> > com.sun.security.sasl.digest.DigestMD5Server.evaluateResponse(DigestMD5Server.java:244) > > > Tony, I assume you are using Spark 2.6.3 > You are experiencing a well known problem of Spark 2.6.3 when xmpp domain > name is different than xmpp fqdn > Spark 2.6.3 is using a SASL DIGEST-MD5 authentication layer and there are > two problems: > > -REALM problem that lies SMACK API that Spark 2.6.3 is using where REALM is > not correctly retrieved > -digest-uri problem that lies in Openfire 3.6.4, 3.7.0 - instantiates a SASL > server with xmpp.domain, but when it sends back the value to the client it > sends xmpp.fqdn > > I have posted patches for both problems > > Please see: > http://issues.igniterealtime.org/browse/SPARK-751 > http://issues.igniterealtime.org/browse/SMACK-344 > http://issues.igniterealtime.org/browse/OF-477 > > Spark 2.5.8 should work because it does not use SASL DIGEST auth layer (I > think it uses PLAIN SASL or the obsolete XMPP auth layer: Non-SASL > Authentication http://xmpp.org/extensions/xep-0078.html) > > Pidgin is working because probably it uses a different authentication Layer > > Hope these info helps, > > Mircea > ---------- > Come and see us at CoLab @ CSU in March (5th & 6th) > http://www.sipfoundry.org/sipx-colab > http://wiki.sipfoundry.org/display/sipXecs/2012+sipX-CoLab+Hackfest > > > _______________________________________________ > sipx-dev mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-dev/ -- ~~~~~~~~~~~~~~~~~~ Tony Graziano, Manager Telephone: 434.984.8430 sip: [email protected] Fax: 434.465.6833 ~~~~~~~~~~~~~~~~~~ LAN/Telephony/Security and Control Systems Helpdesk: Telephone: 434.984.8426 sip: [email protected] Helpdesk Customers: http://myhelp.myitdepartment.net Blog: http://blog.myitdepartment.net Linked-In Profile: http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4 Ask about our Internet Fax services! -- LAN/Telephony/Security and Control Systems Helpdesk: Telephone: 434.984.8426 sip: [email protected] Helpdesk Customers: http://myhelp.myitdepartment.net Blog: http://blog.myitdepartment.net _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev/
