File

spec/scansion/tombstones.scs @ 12997:0a56b84ec4ad

mod_tokenauth: Support for creating sub-tokens Properties of sub-tokens: - They share the same id as their parent token - Sub-tokens may not have their own sub-tokens (but may have sibling tokens) - They always have the same or shorter lifetime compared to their parent token - Revoking a parent token revokes all sub-tokens - Sub-tokens always have the same JID as the parent token - They do not have their own 'accessed' property - accessing a sub-token updates the parent token's accessed time Although this is a generic API, it is designed to at least fill the needs of OAuth2 refresh + access tokens (where the parent token is the refresh token and the sub-tokens are access tokens).
author Matthew Wild <mwild1@gmail.com>
date Sun, 26 Mar 2023 16:46:48 +0100
parent 12116:efcf25ad5406
line wrap: on
line source

# Tombstones

[Client] Romeo
	jid: romeo@localhost
	password: password

[Client] Juliet
	jid: juliet-tombstones@localhost
	password: password

---------

Romeo connects

Juliet connects

Juliet sends:
	<iq type="set" id="bye">
		<query xmlns="jabber:iq:register">
			<remove/>
		</query>
	</iq>

# Scansion gets disconnected right after this with a stream error makes
# scansion itself abort, so we preemptively disconnect to avoid that
# Juliet receives:
#	<iq type="result" id="bye"/>

Juliet disconnects

Romeo sends:
	<presence type="probe" to="${Juliet's JID}"/>

Romeo receives:
	<presence type="error" from="${Juliet's JID}"/>

Romeo receives:
	<presence type="unsubscribed" from="${Juliet's JID}"/>