Express backend settings that are specific to these providers. For everything else, see auth setup.
In the client connector you copied, return the provider's token from the private fetchAuthToken()
method, which supplies both writes and fetchCredentials() (sync). Provider SDKs manage their
own sessions, so you can drop the demo token cache in getAuthToken(). If sync and
writes use different tokens, both must carry the same user ID in sub.
Use a PowerSync Cloud export configured for asymmetric Supabase Auth, following
PowerSync's Supabase setup. The
issuer, audience and JWKS URL are derived for standard hosted projects; a custom domain needs
AUTH_PROVIDER and AUTH_SUPABASE_URL (see auth setup).
Legacy HS256 secrets are rejected. Migrate to Supabase signing keys and re-export.
The Express backend's Postgres adapter exposes the verified token claims through
request.jwt.claims, which Supabase's auth.uid() and auth.jwt() helpers can read. It does
not switch database roles: RLS applies only when the connection role is subject to RLS and
the policies apply to that role. See Postgres row-level security.
The Supabase Edge Function additionally switches to the
authenticated role, so it can use the grants and RLS policies configured for signed-in
Supabase users. It needs none of the Express backend's authentication settings.
Clerk publishes a JWKS endpoint, so use AUTH_MODE=env. Which settings you need depends on the
token you send to the write API.
A JWT template token carries an
aud, so one token can serve sync and writes. Set the template's aud as the audience:
AUTH_MODE=env
AUTH_ISSUER=https://<your-frontend-api>.clerk.accounts.dev
AUTH_AUDIENCE=<the template's aud>
AUTH_JWKS_URI=https://<your-frontend-api>.clerk.accounts.dev/.well-known/jwks.jsonA session token has no aud. The Express backend instead checks azp, the origin of the app that
obtained the token. You still need a template token for sync.
AUTH_MODE=env
AUTH_ISSUER=https://<your-frontend-api>.clerk.accounts.dev
AUTH_JWKS_URI=https://<your-frontend-api>.clerk.accounts.dev/.well-known/jwks.json
AUTH_REQUIRE_AUDIENCE=false
AUTH_AUTHORIZED_PARTIES=http://localhost:5173,https://yourapp.comAUTH_REQUIRE_AUDIENCE=false is accepted only with AUTH_AUTHORIZED_PARTIES; without either
check, any token from your Clerk instance would be valid. Tokens with a missing or unlisted
azp are rejected, so apps whose tokens omit it need a custom verifier.
In the connector, getAuthToken() returns clerk.session.getToken() for session tokens and
fetchCredentials() returns getToken({ template: '<name>' }).