[jdev] Authentication Process For Jabber.com

Peter Saint-Andre stpeter at stpeter.im
Tue Feb 26 01:36:47 CST 2008

shashi kiran wrote:
> Hi All,
> I am Developing a a Jabber Client for Series 60 Nokia Phones. It was written
> so as to Support both GTalk and Jabber.
> For GTalk the Authentication Mechanism used is Either *SASL DIGEST_MD5 or
> SASL PLAIN* which works Fine.

That should work fine at jabber.org too, which is a mostly standard
installation of ejabberd 1.1.4 (soon to be 2.0.0). I can't speak for the
jabber.com service.

> In case of Jabber it only works for some sites. the Login is not working for
> an Account on either *Jabber.com or Jabber.org*
> Infact I am not even getting the list of *Mechanisms* Supported by*
> Jabber.com or Jabber.org.

It would help if you could provide information about the exact XML you
are sending and receiving so that we can help you debug.


-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 7338 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://mail.jabber.org/pipermail/jdev/attachments/20080226/ae9e87af/attachment-0002.bin>

More information about the JDev mailing list