Support SASL2 FAST authentication by kousu · Pull Request #840 · strophe/strophejs

kousu · 2025-06-09T15:40:13Z

FAST is a cookie-style authentication method that lets clients store and auth with an unguesseable token. It enables clients to forget the user's full password, which is especially important for web-based clients, that are prone to data leaks. Leaked tokens can be invalidated.

This my second attempt, and supersedes #839 .

Intended to fix conversejs/converse.js#3144

Some aside changes I needed for this:

I let handlers listen to the opening stanza
Set 'from' on the opening tag. (ref: https://github.com/xmppjs/xmpp.js/pull/1006/files#r1893267922)
Create a type of handler that can search nested data. This made setting up listeners a lot more convenient.
During connection, replace has_features with the direct XML stream:features more direct and defensive.
Moved Status.AUTHENTICATING before FAST/SASL

Testing

On a prosody server, set these modules_enabled:

	-- SASL2/FAST
		"sasl2";
		"sasl2_bind2";
		"sasl2_sm";
		"sasl2_fast";
		"client_management";

Make or pick a test account on your server to test with.

Then run the client with:

git clone -b sasl2_fast_2 git@github.com:kousu/strophejs
git clone -b sasl2_fast_2 git@github.com:kousu/converse.js
cd converse.js

Edit converse.js/dev.html to change the prefilled username to match your server (or just be ready to type it in)

npm ci
npm run serve & npm run watch & xdg-open https://localhost:8080/dev.html

TODO:

Test under both websocket and BOSH
Invalidate token on logout
- In the corresponding Converse.js branch, actually forget the token on logout
Under my over eager autoformatter
support the other HT- methods from the spec
Disentangle the circular dependency between index.js loading sasl2.js/sasl2_fast.js but them needing to talk to Strophe
Check and provide proper copyright notice for the snippet I took from xmpp.js

Potential follow ups:

rewrite the SASL code into an event-based src/sasl.js to make it look like src/sasl2.js
allow fallback from SASL2 to SASL and between SASL methods

(currently assumes only ONE login method will be tried per connect(), which could block login if one is failing)

src/handler.js

src/connection.js

src/bosh.js

src/connection.js

src/handler.js

kousu · 2025-06-09T15:45:37Z

src/connection.js

            }
        );
+
+        return elem;


this is meant to glue into the old non-event-based SASL1 login system

src/connection.js

kousu · 2025-06-09T15:46:27Z

src/sasl-ht-sha256-none.js

+     */
+    // eslint-disable-next-line class-methods-use-this
+    async clientChallenge(connection, test_cnonce) {
+        // from https://github.com/xmppjs/xmpp.js/blob/d01b2f1dcb81c7d2880d1021ca352256675873a4/packages/sasl-ht-sha-256-none/index.js#L12


TODO: check licensing

kousu · 2025-06-09T15:48:07Z

src/sasl2_fast.js

+
+            authenticate.nodeTree.querySelector("fast")?.setAttribute("invalidate", "true")
+
+            this.conn.send(authenticate.tree())


This never gets sent?? maybe because it's sent during disconnection?

Could someone tell me where is a better place to hook into the logout process?

I know you're probably busy @jcbrand (me too!). Perhaps you can just give me a pointer on this logout part. You don't need to review the whole PR yet.

I'm trying to send a logout to the server, which in FAST means sending a stanza using your token to invalidate itself:

<authenticate xmlns='urn:xmpp:sasl:2' mechanism='HT-SHA-256-NONE'> <initial-response>[base64 encoded SASL data]</initial-response> <fast xmlns='urn:xmpp:fast:0' count='123' invalidate='true'/> </authenticate>

but this code happens too late, after the xmpp socket is already closed. Maybe it's racey and succeeds some small percentage of the time, I'm not super sure. I hooked it in with this sketchy code:

strophejs/src/sasl2_fast.js

Lines 116 to 122 in 3ee9a13

// **MONKEY-PATCH** connection to catch the logout event

let reset = this.conn.reset.bind(this.conn)

this.conn.reset = () => {

this.logout.bind(this)().then(() => {

reset()

})

}

Is there a better hook I could use?

Do I to teach ConverseJS to call this logout() function before actually disconnecting? I hoped not, I hoped to contain most of the FAST stuff in one place. I'll do it if you think that's the best way though.

Thanks :)

kousu · 2025-06-09T15:49:44Z

src/websocket.js

        return $build('open', {
            'xmlns': NS.FRAMING,
            'to': this._conn.domain,
+            ...((this._conn.service.startsWith("wss") || this._conn.service.startsWith("ws://localhost")) ? { 'from': this._conn.jid } : {}),


from is mandatory for FAST, but is bad for privacy to send over an unencrypted channel. Split the difference by sending only when over TLS.

https://xmpp.org/extensions/xep-0484.html#rules-clients

Clients wishing to use FAST authentication MUST provide the authenticating JID in the secure stream's 'from' attribute. They MUST also provide the a SASL2 element with an 'id' attribute (both of these values are discussed in more detail in XEP-0388).

kousu · 2025-06-09T15:49:57Z

src/bosh.js


        const body = this._buildBody().attrs({
            'to': this._conn.domain,
+            ...(this._conn.service.startsWith("https://") ? { 'from': this._conn.jid } : {}),


see https://github.com/strophe/strophejs/pull/840/files#r2135979184

kousu · 2025-06-09T15:50:06Z

src/bosh.js

                    if (data[i] === 'restart') {
                        body.attrs({
                            'to': this._conn.domain,
+                            ...(this._conn.service.startsWith("https://") ? { 'from': this._conn.jid } : {}),


ditto https://github.com/strophe/strophejs/pull/840/files#r2135979184

FAST is a cookie-style authentication method that lets clients store and auth with an unguesseable token. It enables clients to forget the user's full password, which is especially important for web-based clients, that are prone to data leaks. Leaked tokens can be invalidated. - https://xmpp.org/extensions/xep-0484.html - https://xmpp.org/extensions/xep-0388.html Intended to fix conversejs/converse.js#3144 Some aside changes I needed for this: - I let handlers listen to the *opening* stanza - Set 'from' on the opening <stream> tag. (ref: https://github.com/xmppjs/xmpp.js/pull/1006/files#r1893267922) - Create a type of handler that can search *nested data*. This made setting up listeners a lot more convenient. - During connection, replace has_features with the direct XML <stream:features> more direct and defensive. - Moved Status.AUTHENTICATING before FAST/SASL Still TODO: - support the other HT- methods from the spec - rewrite the SASL code into sasl.js to look like sasl2.js ? - allow fallback from SASL2 to SASL (currently assumes only ONE login method will be tried per connect(), which could block login if one is failing) - pull SASL2 into sasl2.js and make it a plugin - Disentangle the circular dependency between index.js loading sasl2.js/sasl2_fast.js but them needing to talk to Strophe - Invalidate token on logout (and in the corresponding Converse.js branch, actually forget the token on logout)

kousu · 2025-06-09T17:00:29Z

src/scram.js

+    test: function (connection, hashName, hashBits) {
+        return true; // XXX debug
+        return connection.authcid !== null
+            && (
+                (typeof connection.pass === 'string' || connection.pass instanceof String)
+                || (connection.pass?.name === hashName)
+            );
+    },


This is here to make sure that we don't accidentally try to SCRAM-SHA-1 when we only have a HT-SHA-256-NONE token available.

kousu · 2025-06-09T17:01:44Z

src/sasl2_fast.js

+    logout: async function () {
+        // Invalidate the FAST token on log out
+        // XXX this does not seem to actually get sent,
+        // and Converse does not forget the token from its IndexedDB
+        // if you edit Local Storage using the web debugger to re-add conversejs-session-jid: 'user@xmpp.example.org'
+        // and reload then FAST will happily log you back in
+
+        if (this.credential.token) {
+            let authenticate = await this.conn.sasl2.authenticateStanza(this.credential.mechanism)
+
+            // XXX copy-pasta
+            const response = await this.conn.mechanisms[this.credential.mechanism].clientChallenge(this.conn);
+            authenticate
+                .c('initial-response',
+                    null,
+                    btoa(/** @type {string} */(response)))
+                .up();
+
+            authenticate.nodeTree.querySelector("fast")?.setAttribute("invalidate", "true")


This whole thing doesn't work. In conversejs/converse.js#3693 I made sure the token gets forgotten on logout, so it's not the worst, but it would be ideal to invalidate tokens we're not using.

src/sasl2.js

src/connection.js

src/scram.js

jcbrand · 2025-08-28T14:59:38Z

Hi @kousu

Thanks a lot for all your effort in making this PR.
I read the two XEPs and went through this PR now for the first time and left some review comments.

kousu · 2025-09-28T01:20:51Z

Thank you for taking a look.
I got really really busy in September. This fell off my radar. I definitely still care, since I have it deployed in production and I'd like to upstream what I did (and get it cleaned up too :P), but I don't have a horizon for when I'll have the energy to get around to it. I'll set myself a reminder to check in every couple weeks.

kousu · 2025-11-09T23:52:26Z

Sorry this is stuck in the mud. Still getting my butt kicked by papers and simulations. But I want to get back to it!

kousu mentioned this pull request Jun 9, 2025

[WIP] Support SASL2 FAST authentication #839

Closed

kousu marked this pull request as ready for review June 9, 2025 15:40