moparisthebest/xeps
1
0
Fork 0
mirror of https://github.com/moparisthebest/xeps synced 2025-03-03 10:02:00 -05:00
Code Issues Releases Wiki Activity

XEP-0389: add an IQ query for flows

Browse Source
This commit is contained in:
Sam Whited 2020-04-22 11:28:11 -04:00
parent 12396476b8
commit 1f904b69be
1 changed files with 49 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

51
xep-0389.xml
View File

@ -264,8 +264,55 @@
fact by including a feature of "urn::xmpp:register:0" in response to fact by including a feature of "urn::xmpp:register:0" in response to
&xep0030; information requests and in their &xep0115; profiles. &xep0030; information requests and in their &xep0115; profiles.
</p> </p>
<example caption='Disco response'><![CDATA[ <example caption='Disco info response'><![CDATA[
<feature var='urn:xmpp:register:0' />]]></example> <query xmlns='http://jabber.org/protocol/disco#info'>
…
<feature var='urn:xmpp:register:0' />
…
</query>]]></example>
</section2>
<section2 topic='Retrieving the Flows'>
<p>
To find what flows an entity provides (if any) after stream negotiation is
complete the requester can send an IQ of type "get" containing a
&lt;register&gt; or &lt;recovery&gt; element qualified by the
"urn:xmpp:register:0" namespace.
</p>
<p>
When responding to a query for registration or recovery flows the list of
challenges should be included just as it would be if during stream feature
negotiation.
That is, a "register" or "recovery" element containing a list of flows,
each with an id, containing a name and a list of challenges.
If an entity supports this specification but does not provide any flows
after stream negotiation it MUST respond with an empty list.
</p>
<example caption='Registration flows query'><![CDATA[
<iq type='get'>
<register xmlns='urn:xmpp:register:0'/>
</iq>]]></example>
<example caption='Registration flows results'><![CDATA[
<iq type='result'>
<register xmlns='urn:xmpp:register:0'>
<flow id='0'>
<name>Verify with SMS</name>
<challenge type='jabber:x:data'/>
</flow>
<flow id='1'>
<name>Verify by Phone Call</name>
<challenge type='jabber:x:data'/>
</flow>
<flow id='2'>
<name>Verify with the web</name>
<challenge type='jabber:x:data'/>
<challenge type='jabber:x:oob'/>
</flow>
</register>
</iq>]]></example>
<example caption='Empty registration flows results'><![CDATA[
<iq type='result'>
<register xmlns='urn:xmpp:register:0'/>
</iq>]]></example>
</section2> </section2>
</section1> </section1>
<section1 topic='Challenges' anchor='challenge'> <section1 topic='Challenges' anchor='challenge'>