On Sat, Jan 28, 2012 at 9:47 AM, Mircea Carasel <[email protected]> wrote: > > > On Sat, Jan 28, 2012 at 4:10 PM, Tony Graziano > <[email protected]> wrote: >> >> 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? >> > > I have been contributing to Spark pretty much in the past few months, and I > helped them to launch SPARK 2.7.0 beta 1 > I very much wanted to include the SASL fix in there, as this would have > helped the whole Spark community and others, that are > doing serious Spark testing in large enterprise environments > In order to make everything more flexible, I implemented a pluggable > mechanism in SPARK 2.7.0 that lets you change the authentication layer, but > you have to build a spark plugin and deploy in spark > > Unfortunately the authentication layer in Spark is not something that you > can configure, a checkbox/combobox or something that you can click and pick > what authentication you want. Spark 2.6.3 > > The only thing that you can do is to launch the openfire console, go to > first page: Server Settings and change xmpp.domain openfire property to be > the same as xmpp.fqdn > this workarounds the digest-uri issue on openfire, but it still remains the > REALM problem that lies in SMACK > I see that works. It does require all contacts to be re-added manually, etc. So sticking with Pidgin is an easier thing since we need multiple updates from the openfire community to make this work as desired. It also seems we'll have to wait for openfire AND spark updates from them and it might take some time to get all of those in and functional.
Thanks for helping me to fully understand the issues here. > > 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/
