File

spec/scansion/uptime.scs @ 12938:055b03d3059b

util.sasl.oauthbearer: Return username from callback instead using authzid (BC) RFC 6120 states that > If the initiating entity does not wish to act on behalf of another > entity, it MUST NOT provide an authorization identity. Thus it seems weird to require it here. We can instead expect an username from the token data passed back from the profile. This follows the practice of util.sasl.external where the profile callback returns the selected username, making the authentication module responsible for extracting the username from the token.
author Kim Alvefur <zash@zash.se>
date Thu, 16 Mar 2023 12:18:23 +0100
parent 10731:8e2f9d0fa72d
child 13405:c8f3cfe59e90
line wrap: on
line source

# XEP-0012: Last Activity / mod_uptime

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

-----

Romeo connects

Romeo sends:
	<iq id='a' type='get' to='localhost'>
		<query xmlns='jabber:iq:last'/>
	</iq>

Romeo receives:
	<iq type='result' id='a' from='localhost'>
		<query xmlns='jabber:iq:last' seconds='0'/>
	</iq>

Romeo disconnects