moparisthebest
/
xeps
mirror of https://github.com/moparisthebest/xeps
1
0
Fork 0
Code Issues Releases Wiki Activity

# This is a combination of 2 commits. 

# The first commit's message is:

Initial version of token reconnection extension

# The 2nd commit message will be skipped:

#	Switch to XEP-allowed tags (a -> link, b -> strong)
This commit is contained in:
Michal Piotrowski 2016-02-04 14:11:13 +01:00 committed by Matthew A. Miller
parent 7df7f4dc6b
commit f615bd7bc9
1 changed files with 8 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
inbox/token-reconnection.xml
View File

@ -7,7 +7,7 @@
<xep>
<header>
<title>Token-based reconnection</title>
<abstract>This specification defines a token-based session authentication mechanism similar to OAuth.</abstract>
<abstract>This specification defines a token-based session authentication mechanism.</abstract>
<legal>
<copyright>This XMPP Extension Protocol is copyright (c) 1999 - 2016 by the XMPP Standards Foundation (XSF).</copyright>
<permissions>Permission is hereby granted, free of charge, to any person obtaining a copy of this specification (the &quot;Specification&quot;), to make use of the Specification without restriction, including without limitation the rights to implement the Specification in a software program, deploy the Specification in a network service, and copy, modify, merge, publish, translate, distribute, sublicense, or sell copies of the Specification, and to permit persons to whom the Specification is furnished to do so, subject to the condition that the foregoing copyright notice and this permission notice shall be included in all copies or substantial portions of the Specification. Unless separate permission is granted, modified works that are redistributed shall not contain misleading information regarding the authors, title, number, or publisher of the Specification, and shall not claim endorsement of the modified works by the authors, any organization or project to which the authors belong, or the XMPP Standards Foundation.</permissions>
@ -37,6 +37,12 @@
<surname>Szymczyszyn</surname>
<email>radoslaw.szymczyszyn@erlang-solutions.com</email>
</author>
<revision>
<version>0.0.2</version>
<date>2016-02-16</date>
<initials>mp</initials>
<remark><p>Removed mention of OAuth from Abstract; removed mention of DIGEST-MD5.</p></remark>
</revision>
<revision>
<version>0.0.1</version>
<date>2016-02-04</date>
@ -49,7 +55,7 @@
<p>Moreover, while reconnecting to the XMPP server, the client usually has to go through the same long process of SASL challenge-response exchange which may lead to a noticably long reconnection time, especially while using SCRAM-based mechanisms. Providing a token to the XMPP server is both secure and doesn't require multiple challenge-response roundtrips, therefore might significantly speed up reconnection times.</p>
</section1>
<section1 topic='Requirements' anchor='reqs'>
<p>This extension requires the client application to authenticate to the XMPP server using a regular XMPP authentication mechanism like SCRAM-SHA-1 or DIGEST-MD5 at least once. After that, the following authentications may be done using X-OAUTH SASL mechanism with a token obtained from the server.</p>
<p>This extension requires the client application to authenticate to the XMPP server using a regular XMPP authentication mechanism like SCRAM-SHA-1 at least once. After that, the following authentications may be done using X-OAUTH SASL mechanism with a token obtained from the server.</p>
</section1>
<section1 topic='Glossary' anchor='glossary'>
<section2 topic="Token types" anchor="token_types">