Hi JD!
JD Conley schrieb:
There are actually two paths the exchange might take. The SASL PLAIN
payload may be included in the mechanism element by the client as an
initial response (and this is the recommended method). However, it is
not required. So if you’re building a server you need to
The element containing the initial response is not mechanism/ but
auth/. The initial exchange would therefore look something like this:
Oops. :)
-JD
Yeah, thats it. You can test client implementations against our
public server at soapbox.net if you want.
-JD
From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Tong
Sent: Monday, July 31, 2006 8:34 PM
To: jdev@jabber.org
Subject: [jdev] Re: sasl plain
Ok, I think
: [jdev] Re: sasl plain
Yeah, thats it. You can test client implementations against our
public server at soapbox.net if you want.
-JD
From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Tong
Sent: Monday, July 31, 2006 8:34 PM
To: jdev@jabber.org
Subject: [jdev] Re: sasl
Conley
*Sent:* Monday, July 31, 2006 8:55 PM
*To:* Jabber software development list
*Subject:* RE: [jdev] Re: sasl plain
Yeah, that’s it. You can test client implementations against our public
server at soapbox.net if you want.
-JD
*From:* [EMAIL PROTECTED] [mailto:[EMAIL
