Conley, forgives for my ignorancia but I did not understand very well.
I read RFC 3920, but still I did not understand:
The RFC 3920 says:
1.. The initiating entity selects a mechanism by sending an <auth/> element
qualified by the 'urn:ietf:params:xml:ns:xmpp-sasl' namespace to the receiving
entity and including an appropriate value for the 'mechanism' attribute. This
element MAY contain XML character data (in SASL terminology, the "initial
response") if the mechanism supports or requires it; if the initiating entity
needs to send a zero-length initial response, it MUST transmit the response as
a single equals sign ("="), which indicates that the response is present but
contains no data.
But I did not understand what is xml character data. You could give an example
to me please ?
Thx
Alexandre
Brazil
----- Original Message -----
From: JD Conley
To: Jabber software development list
Sent: Wednesday, November 15, 2006 1:45 PM
Subject: RE: [jdev] Incorrect Encoding
It looks like Google is requiring the initial response be sent. See section
6.2 in RFC 3920.
-JD
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of ARP
Sent: Wednesday, November 15, 2006 8:25 AM
To: Jabber software development list
Subject: [jdev] Incorrect Encoding
Hi Guys,
Well, I am trying make a auth in talk.google.com, but I am having some
problems.
When I receive from the server:
<?xml version="1.0" encoding="UTF-8"?>
<stream:stream from="gmail.com" id="CC83300E366C0B75" version="1.0">
xmlns:stream="http://etherx.jabber.org/streams"; xmlns="jabber:client">
<stream:features>
<mechanisms xmlns="urn:ietf:params:xml:ns:xmpp-sasl">
<mechanism>
PLAIN</mechanism>
<mechanism>
X-GOOGLE-TOKEN</mechanism>
</mechanisms>
</stream:features>
I answer with:
<auth xmlns="urn:ietf:params:xml:ns:xmpp-sasl" mechanism="PLAIN"/>
But the server sends to me:
<failure xmlns="urn:ietf:params:xml:ns:xmpp-sasl">
<incorrect-encoding/>
</failure>
</stream:stream>
Why this is happening ?
Please give some help
Thx
Alexandre
Brazil
