Client SDK to request a Beams Token from your backend server

[ddhanak]

Allow passing in the beams token when setting userId (instead of fetching from tokenProvider).

https://github.com/pusher/push-notifications-web/blob/master/src/push-notifications.js#L328

Use case: we have implemented our own logic to fetch the beams token (and we do not want to use the TokenProvider class that sends a request for us through the SDK).

[ddhanak]

@benw-pusher hi ben, is it possible to know if this will be prioritized or not?

[benw-pusher]

I have shared the feedback internally but at this time we cannot commit to a release.

[ddhanak]

@benw-pusher hi any news on this? it has been more than a year now.

[benw-pusher]

Unfortunately, at this time we don't have this work scheduled.

[daniel-shuy]

Actually, this is already possible.

Client.setUserId() takes in an interface (ITokenProvider):

push-notifications-web/index.d.ts

Line 42 in 691ee32

setUserId(userId: string, tokenProvider: ITokenProvider): Promise<undefined>;

push-notifications-web/index.d.ts

Lines 4 to 6 in 691ee32

	export interface ITokenProvider {
	fetchToken(userId: string): Promise<TokenProviderResponse>;
	}

push-notifications-web/index.d.ts

Lines 1 to 3 in 691ee32

	export interface TokenProviderResponse {
	token: string;
	}

You'll just need to create your own ITokenProvider implementation that returns the token immediately, e.g.

client.setUserId(userId, {
  fetchToken: () => Promise.resolve({ token }),
});

[lukepearce]

I have tried multiple versions of the custom ITokenProvider approach, and it's working locally (I can see "Device paired with User" in the Pusher debug console) but when it's deployed to prod, I get Error: Unexpected status code 401: Unauthorized, Invalid JWT signature.

The token is being returned by my server and when decoded, it is the same shape as it is locally.

Any idea what might be happening?