File

spec/scansion/empty_bookmarks.scs @ 12696:27a72982e331

util.jwt: Add support/tests for ES256 via improved API and using util.crypto In many cases code will be either signing or verifying. With asymmetric algorithms it's clearer and more efficient to just state that once, instead of passing keys (and possibly other parameters) with every sign/verify call. This also allows earlier validation of the key used. The previous (HS256-only) sign/verify methods continue to be exposed for backwards-compatibility.
author Matthew Wild <mwild1@gmail.com>
date Fri, 01 Jul 2022 18:51:15 +0100
parent 12593:1832b6c9c6ed
line wrap: on
line source

# mod_scansion_record on host 'localhost' recording started 2022-07-26T21:39:55Z

[Client] Romeo
	password: password
	jid: juliet@localhost/UaksS4M1xYZB

-----

Romeo connects

Romeo sends:
	<iq xml:lang='en' type='get' id='bNBJLtpIJXpq'>
		<pubsub xmlns='http://jabber.org/protocol/pubsub'>
			<items node='storage:bookmarks'/>
		</pubsub>
	</iq>

Romeo receives:
	<iq id='bNBJLtpIJXpq' type='error'>
		<error type='cancel'>
			<item-not-found xmlns='urn:ietf:params:xml:ns:xmpp-stanzas'/>
		</error>
	</iq>

Romeo disconnects

# recording ended on 2022-07-26T21:40:45Z