prosody
055b03d3059b
spec/scansion/mam_prefs_prep.scs

Find changesets by keywords by author, files, the commit message, revision number or hash, or revset expression.

Software / code / prosody

File

spec/scansion/mam_prefs_prep.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 11727:f3aee8a825cc
line wrap: on
line source

# mod_mam should apply JIDprep in prefs

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

-----

Romeo connects

Romeo sends:
	<iq id="lx2" type="set">
		<prefs xmlns="urn:xmpp:mam:2" default="roster">
			<always>
				<jid>JULIET@MONTAGUE.LIT</jid>
			</always>
			<never>
				<jid>MONTAGUE@MONTAGUE.LIT</jid>
			</never>
		</prefs>
	</iq>

Romeo receives:
	<iq id="lx2" type="result">
		<prefs xmlns="urn:xmpp:mam:2" default="roster">
			<always>
				<jid>juliet@montague.lit</jid>
			</always>
			<never>
				<jid>montague@montague.lit</jid>
			</never>
		</prefs>
	</iq>

Romeo disconnects