moparisthebest/xeps
1
0
Fork 0
mirror of https://github.com/moparisthebest/xeps synced 2024-11-21 08:45:04 -05:00
Code Issues Releases Wiki Activity

XEP-0389: error if client selects an invalid flow

Browse Source
This commit is contained in:
Sam Whited 2020-11-14 08:31:45 -05:00
parent a556d9f5ea
commit 9475423c59
1 changed files with 29 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

31
xep-0389.xml
View File

@ -371,7 +371,7 @@
<register xmlns='urn:xmpp:register:0'/> <register xmlns='urn:xmpp:register:0'/>
</iq>]]></example> </iq>]]></example>
</section2> </section2>
<section2 topic='Issuing Challenges' anchor='challenge'> <section2 topic='Selecting a Flow' anchor='selecting'>
<p> <p>
A client selects the registration or recovery feature for negotiation by A client selects the registration or recovery feature for negotiation by
replying with an element of the same name and namespace. replying with an element of the same name and namespace.
@ -384,6 +384,19 @@
<register xmlns='urn:xmpp:register:0'> <register xmlns='urn:xmpp:register:0'>
<flow id='1'/> <flow id='1'/>
</register>]]></example> </register>]]></example>
<p>
If during stream initialization the client attempts to select a flow that
does not match one of the flows sent by the server, the server MUST
respond with an "undefined-condition" stream error containing an
"invalid-flow" application error qualified by the 'urn:xmpp:register:0'
namespace.
</p>
<example caption='Server responds to an invalid selection during stream negotiation'><![CDATA[
<stream:error>
<undefined-condition xmlns='urn:ietf:params:xml:ns:xmpp-streams'/>
<invalid-flow xmlns='urn:xmpp:register:0'/>
</stream:error>
</stream:stream>]]></example>
<p> <p>
If the client is initiating registration or recovery after a stream has If the client is initiating registration or recovery after a stream has
already been initiated it uses the same registration element wrapped in an already been initiated it uses the same registration element wrapped in an
@ -396,7 +409,21 @@
</recovery> </recovery>
</iq>]]></example> </iq>]]></example>
<p> <p>
The server then replies to the IQ or feature selection with a challenge. If the client attempts to select a flow that does not match one of the
flows sent by the server in response to an IQ after stream initialization
the server MUST respond with a stanza error of type "item-not-found".
</p>
<example caption='Server responds to an invalid selection after stream negotiation'><![CDATA[
<iq type='error'>
<error type='cancel'>
<item-not-found xmlns='urn:ietf:params:xml:ns:xmpp-stanzas'/>
</error>
</iq>]]></example>
</section2>
<section2 topic='Issuing Challenges' anchor='challenge'>
<p>
If a valid flow is selected by the client the server then replies to the
IQ or feature selection with a challenge.
If replying to an IQ, the challenge must be wrapped in an IQ of type If replying to an IQ, the challenge must be wrapped in an IQ of type
"result". "result".
Challenges take the form of a &lt;challenge/&gt; element qualified by the Challenges take the form of a &lt;challenge/&gt; element qualified by the