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 also handle an empty <mechanism> element, send back an empty <challenge>, and expect a <response> with the payload.
The element containing the initial response is not <mechanism/> but <auth/>. The initial exchange would therefore look something like this:
<auth xmlns='urn:ietf:params:xml:ns:xmpp-sasl' mechanism='PLAIN'>WW91IHNob3VsZCBub3QgdXNlIFBMQUlOIG9uIGVuZW5jcnlwdGVkIGNoYW5uZWxzLg==</auth>
Tot kijk Matthias