Skip to content
5 changes: 5 additions & 0 deletions .changeset/new-fishes-rescue.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,5 @@
---
'@clerk/clerk-js': patch
---

Bug fix: Broadcast a sign out event to all opened tabs when `Clerk.signOut()` or `User.delete()` is called.
12 changes: 8 additions & 4 deletions integration/testUtils/index.ts
Original file line number Diff line number Diff line change
Expand Up @@ -36,10 +36,14 @@ const createExpectPageObject = ({ page }: TestArgs) => {
expect(redirect.status()).toBe(307);
expect(redirect.headers()['x-clerk-auth-status']).toContain('handshake');
},
toBeSignedOut: () => {
return page.waitForFunction(() => {
return !window.Clerk?.user;
});
toBeSignedOut: (args?: { timeOut: number }) => {
return page.waitForFunction(
() => {
return !window.Clerk?.user;
},
null,
{ timeout: args?.timeOut },
);
},
toBeSignedIn: async () => {
return page.waitForFunction(() => {
Expand Down
2 changes: 1 addition & 1 deletion integration/tests/sign-out-smoke.test.ts
Original file line number Diff line number Diff line change
Expand Up @@ -55,7 +55,7 @@ testAgainstRunningApps({ withEnv: [appConfigs.envs.withEmailCodes] })('sign out
await m.po.expect.toBeSignedOut();
});

await mainTab.po.expect.toBeSignedOut();
await mainTab.po.expect.toBeSignedOut({ timeOut: 2 * 1_000 });
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Previously the test was passing after 40-50 seconds because either /touch or /tokens would force update the state.

});

test('sign out persisting client', async ({ page, context }) => {
Expand Down
30 changes: 16 additions & 14 deletions packages/clerk-js/src/core/clerk.ts
Original file line number Diff line number Diff line change
Expand Up @@ -374,6 +374,9 @@ export class Clerk implements ClerkInterface {

const handleSetActive = () => {
const signOutCallback = typeof callbackOrOptions === 'function' ? callbackOrOptions : undefined;

// Notify other tabs that user is signing out.
eventBus.dispatch(events.UserSignOut, null);
Comment on lines +378 to +379
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

❓ should we be doing this later in the sign out flow?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Previously inside setActive it was one of the first things that got called. And since by that point we have already cleared cookies seems appropriate.

if (signOutCallback) {
return this.setActive({
session: null,
Expand Down Expand Up @@ -908,14 +911,6 @@ export class Clerk implements ClerkInterface {

await onBeforeSetActive();

// If this.session exists, then signOut was triggered by the current tab
// and should emit. Other tabs should not emit the same event again
const shouldSignOutSession = this.session && newSession === null;
if (shouldSignOutSession) {
this.#broadcastSignOutEvent();
eventBus.dispatch(events.TokenUpdate, { token: null });
}

Comment on lines -911 to -918
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Since we are no longer delete the client on sign out, this.session would always be null, causing broadcasting to never occur.

Also removing eventBus.dispatch(events.TokenUpdate, { token: null }) does not cause issues, because the code a few lines below will handle it appropriately.

//1. setLastActiveSession to passed user session (add a param).
// Note that this will also update the session's active organization
// id.
Expand Down Expand Up @@ -1534,6 +1529,7 @@ export class Clerk implements ClerkInterface {
});
};

// TODO: Deprecate this one, and mark it as internal. Is there actual benefit for external developers to use this ? Should they ever reach for it ?
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What do you think about this ? Would we ever ask people to use this in a custom flow ?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Most likely not, it should really be something that's handled internally.

public handleUnauthenticated = async (opts = { broadcast: true }): Promise<unknown> => {
if (!this.client || !this.session) {
return;
Expand All @@ -1545,7 +1541,7 @@ export class Clerk implements ClerkInterface {
return;
}
if (opts.broadcast) {
this.#broadcastSignOutEvent();
eventBus.dispatch(events.UserSignOut, null);
}
return this.setActive({ session: null });
} catch (err) {
Expand Down Expand Up @@ -2061,11 +2057,21 @@ export class Clerk implements ClerkInterface {
this.#sessionTouchOfflineScheduler.schedule(performTouch);
});

/**
* Background tabs get notified of a signout event from active tab.
*/
this.#broadcastChannel?.addEventListener('message', ({ data }) => {
if (data.type === 'signout') {
void this.handleUnauthenticated();
void this.handleUnauthenticated({ broadcast: false });
}
});

/**
* Allow resources within the singleton to notify other tabs about a signout event (scoped to a single tab)
*/
eventBus.on(events.UserSignOut, () => {
this.#broadcastChannel?.postMessage({ type: 'signout' });
});
};

// TODO: Be more conservative about touches. Throttle, don't touch when only one user, etc
Expand Down Expand Up @@ -2100,10 +2106,6 @@ export class Clerk implements ClerkInterface {
}
};

#broadcastSignOutEvent = () => {
this.#broadcastChannel?.postMessage({ type: 'signout' });
};

#setTransitiveState = () => {
this.session = undefined;
this.organization = undefined;
Expand Down
2 changes: 2 additions & 0 deletions packages/clerk-js/src/core/events.ts
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,7 @@ import type { TokenResource } from '@clerk/types';

export const events = {
TokenUpdate: 'token:update',
UserSignOut: 'user:signOut',
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💭 (optional) what do you think about just calling this even signOut? I'm not sure we need the user: scope.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I was thinking the same, I added the scope to respect the pattern. Since it does not do any harm, I think I'll leave it as is.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fair enough, I wouldn't say 1 event indicates a pattern though 😉

} as const;

type ClerkEvent = (typeof events)[keyof typeof events];
Expand All @@ -11,6 +12,7 @@ type TokenUpdatePayload = { token: TokenResource | null };

type EventPayload = {
[events.TokenUpdate]: TokenUpdatePayload;
[events.UserSignOut]: null;
};

const createEventBus = () => {
Expand Down
5 changes: 4 additions & 1 deletion packages/clerk-js/src/core/resources/Client.ts
Original file line number Diff line number Diff line change
Expand Up @@ -83,7 +83,10 @@ export class Client extends BaseResource implements ClientResource {
removeSessions(): Promise<ClientResource> {
return this._baseDelete({
path: this.path() + '/sessions',
}) as unknown as Promise<ClientResource>;
}).then(e => {
SessionTokenCache.clear();
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think this is the right place for this call. What's the desired behavior? SessionTokenCache is cleared on sign out?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Correct, clearing the cache on sign out.

We're calling SessionTokenCache.clear() on Client.destroy(), on Session.end(), and on Session.remove(). Giving the fact that we clear the cache on an individual session removal, i think we should do the same when removing all of them.

return e as unknown as ClientResource;
});
}

clearCache(): void {
Expand Down
6 changes: 5 additions & 1 deletion packages/clerk-js/src/core/resources/User.ts
Original file line number Diff line number Diff line change
Expand Up @@ -35,6 +35,7 @@ import type {
import { unixEpochToDate } from '../../utils/date';
import { normalizeUnsafeMetadata } from '../../utils/resourceParams';
import { getFullName } from '../../utils/user';
import { eventBus, events } from '../events';
import { BackupCode } from './BackupCode';
import {
BaseResource,
Expand Down Expand Up @@ -241,7 +242,10 @@ export class User extends BaseResource implements UserResource {
};

delete = (): Promise<void> => {
return this._baseDelete({ path: '/me' });
return this._baseDelete({ path: '/me' }).then(res => {
eventBus.dispatch(events.UserSignOut, null);
return res;
});
};

getSessions = async (): Promise<SessionWithActivities[]> => {
Expand Down