I used that too : <auth xmlns='urn:ietf:params:xml:ns:xmpp-sasl'mechanism='PLAIN'/> I inserted the space just to see if it makes any difference. The interesting thing is that if I try : <auth xmlns='urn:ietf:params:xml:ns:xmpp-sasl'mechanism='DIGEST-MD5'/> server sends me a challenge instead of failure. But I don't want to go through that  MD5 jungle. Norman Rasmussen <norman@rasmussen.co.za> wrote:<blockquote class="replbq" style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; padding-left: 5px;"> shouldn't:<auth xmlns="urn:ietf:params:xml:ns:xmpp-sasl" mechanism="PLAIN">be <auth xmlns="urn:ietf:params:xml:ns:xmpp-sasl" mechanism="PLAIN"><auth xmlns='urn:ietf:params:xml:ns:xmpp-sasl'mechanism='PLAIN'/> are you missing the space? On 3/22/06, Adrian Adrian <flashbk2003 @yahoo.com=""> wrote: > Hello, > > I want to comunicate with and IM server (Wildfire) through TLS on port 5222 > using SASL plain text authentication according to RFC 3920 > > Basically I start a stream, server shows me the auth mechanisms, I send > startls command, server says proceed, I start a new stream, server shows me > the auth mechanisms, I select PLAIN and the server shuts me off. > > > Here's the communication : > > CLIENT : <flash:stream to="192.168.11.3"> > xmlns="jabber:client" > xmlns:flash="http://www.jabber.com/streams/flash" > version="1.0"> > SERVER <flash:stream =""> > xmlns:flash="http://www.jabber.com/streams/flash" > xmlns:stream="http://etherx.jabber.org/streams" > xmlns="jabber:client" from="192.168.11.3" id="5bbdf7a3" xml:lang="en" > version="1.0"><stream:features><starttls =""> > xmlns="urn:ietf:params:xml:ns:xmpp-tls"></starttls><mechanisms =""> > xmlns="urn:ietf:params:xml:ns:xmpp-sasl"><mechanism>CRAM-MD5</mechanism><mechanism>DIGEST-MD5</mechanism><mechanism>PLAIN</mechanism><mechanism>ANONYMOUS</mechanism></mechanisms><auth =""> > xmlns="http://jabber.org/features/iq-auth"/><register =""> > xmlns="http://jabber.org/features/iq-register"/></register> > CLIENT <starttls xmlns="urn:ietf:params:xml:ns:xmpp-tls"> > SERVER <proceed xmlns="urn:ietf:params:xml:ns:xmpp-tls"> > CLIENT <flash:stream to="192.168.11.3"> > xmlns="jabber:client" > xmlns:flash="http://www.jabber.com/streams/flash" > version="1.0"> > SERVER <flash:stream =""> > xmlns:flash="http://www.jabber.com/streams/flash" > xmlns:stream="http://etherx.jabber.org/streams" > xmlns="jabber:client" from="192.168.11.3" id="e6661ae8" xml:lang="en" > version="1.0"><stream:features><starttls =""> > xmlns="urn:ietf:params:xml:ns:xmpp-tls"></starttls><mechanisms =""> > xmlns="urn:ietf:params:xml:ns:xmpp-sasl"><mechanism>CRAM-MD5</mechanism><mechanism>DIGEST-MD5</mechanism><mechanism>PLAIN</mechanism><mechanism>ANONYMOUS</mechanism></mechanisms><auth =""> > xmlns="http://jabber.org/features/iq-auth"/><register =""> > xmlns="http://jabber.org/features/iq-register"/></register> > CLIENT <auth =""> > xmlns='urn:ietf:params:xml:ns:xmpp-sasl'mechanism='PLAIN'/> > SERVER <failure =""> > xmlns="urn:ietf:params:xml:ns:xmpp-sasl"><not-authorized></not-authorized> > > As you can see, although the server advertises the PLAIN mechanism, it > doesn't let me connect to it. Why ? > > Thanks. > > PS here's the wildfire error log : > > > > > > > > ________________________________ > Yahoo! Mail > Bring photos to life! New PhotoMail makes sharing a breeze. > > -- - Norman Rasmussen - Email: norman@rasmussen.co.za - Home page: http://norman.rasmussen.co.za/ </failure></auth></auth></stream:features></flash:stream></flash:stream></proceed></starttls></auth></stream:features></flash:stream></flash:stream></flashbk2003></auth></auth></blockquote> <hr size=1>Yahoo! Travel <a href="http://us.lrd.yahoo.com/_ylc=X3oDMTFscDlocTFiBF9TAzMyOTc1MDIEX3MDMjcxOTQ4MQRwb3MDMgRzZWMDbWFpbC1mb290ZXIEc2xrA3l0LXR0/SIG=12hqieud9/**http%3a//leisure.travelocity.com/Promotions/0,,YHOE%7c1381%7cvacs_main,00.html">Find great deals</a> to the top 10 hottest destinations!