Problems with JabberHTTPBind and suggestions

[Lokesh Bathija]

Hi Steve,

1) The JabberHTTPBind0.3 at present does not provide support for SASL
Anonymous Login, but JsJac-0.5 supports SASL Anonymous Login.

2) Also the JHBServlet while doing stream negotiation does not send version,
    which defaults to version 0.0. For SASL Anon the version should be
sent as 1.0.

Suggestions:
1) As i suggested to you before, start a wiki for Documents, as i have
the documents ready.

2) I am also currently working on JsJac and JabberHTTPBind, so i would
appreciate that if you
    can provide me with the access to current code(including the
changes that you keep       making) so that the effort is not
duplicated and wasted.

Regards,
Lokesh.


-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642
_______________________________________________
JWChat-devel mailing list
JWChat-devel@...
https://lists.sourceforge.net/lists/listinfo/jwchat-devel

[Stefan Strigler]

Hi,

Am Freitag, den 24.02.2006, 18:42 +0530 schrieb Lokesh Bathija:

> 1) The JabberHTTPBind0.3 at present does not provide support for SASL
> Anonymous Login, but JsJac-0.5 supports SASL Anonymous Login.

jsjac-0.5 support sasl anonymous for http polling only.

> 2) Also the JHBServlet while doing stream negotiation does not send version,
>     which defaults to version 0.0. For SASL Anon the version should be
> sent as 1.0.

The problem with that is that SASL authentication is not implemented at
jsjac currently. If a connection manager sends an xmpp compliant header
to an xmpp compliant server like ejabberd it does not allow non-sasl
authentication (this is true at least for ejabberd). Thus it doesn't
make sense to let the JHBServlet send a stream header with version='1.0'
set here.


> Suggestions:
> 1) As i suggested to you before, start a wiki for Documents, as i have
> the documents ready.

Could you please ask for an account at wiki.jabber.org (I think stpeter
is the person to contact for this though no responsibility is mentioned
anywhere at this place)?

> 2) I am also currently working on JsJac and JabberHTTPBind, so i would
> appreciate that if you
>     can provide me with the access to current code(including the
> changes that you keep       making) so that the effort is not
> duplicated and wasted.

There's a public CVS repository for jsjac which you could use to keep
up2date, I'll try to setup a public repository for JHB too within the
next days, so stay tuned.

Cheers, Steve



-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
JWChat-devel mailing list
JWChat-devel@...
https://lists.sourceforge.net/lists/listinfo/jwchat-devel

[BurningIce]

Lokesh Bathija wrote:

Hi Steve,

1) The JabberHTTPBind0.3 at present does not provide support for SASL
Anonymous Login, but JsJac-0.5 supports SASL Anonymous Login.

I don't understand what do you mean by JabberHTTPBind0.3 at present does not provide support for SASL
Anonymous Login? Doesn't it just act a act as a proxy to forward all xml-stanzas to the actual XMPP server.
I think whether it supports SASL Anonymous Login is up to whe XMPP server. Isn't it?

[Stefan Strigler]

Am Samstag, den 21.10.2006, 04:15 -0700 schrieb BurningIce:

>
>
> Lokesh Bathija wrote:
> >
> > Hi Steve,
> >
> > 1) The JabberHTTPBind0.3 at present does not provide support for SASL
> > Anonymous Login, but JsJac-0.5 supports SASL Anonymous Login.
> >
>
> I don't understand what do you mean by JabberHTTPBind0.3 at present does not
> provide support for SASL
> Anonymous Login? Doesn't it just act a act as a proxy to forward all
> xml-stanzas to the actual XMPP server.
> I think whether it supports SASL Anonymous Login is up to whe XMPP server.
> Isn't it?
>

Yes and no. The problem arises out of the circumstance that it's the
connection manager (JHB servlet) that sends the initiating XML stream
element to the jabber server and thus it's where it's being decided
whether it's got a "version='1.0'" in it or not. Which in turn impacts
on how the client has to authenticate.

I had a talk to Ian on this topic yesterday and he agreed on adding
support for

a) empowering the client to indicate which stream version to be used
b) having an extra option to indicate the connection manager to
reinitialize a stream as required by SASL authentication

Next version of JabberHTTPBind will have those new features implemented.
(Actually I've implemented it yesterday, but an updated version of the
XEP is not published yet)

Cheers, Steve


-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
JWChat-devel mailing list
JWChat-devel@...
https://lists.sourceforge.net/lists/listinfo/jwchat-devel