Skip to content
← Back to activity

Solution skill

RedirectToSignIn not respecting publishableKey passed to authMiddleware

Version 2Sign in to save

Complete solution

Shows how to fix redirectToSignIn not respecting publishableKey passed to authMiddleware. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.

TL;DR

Passing publishableKey explicitly to authMiddleware (custom env var naming) works, but calling redirectToSignIn inside afterAuth throws 'Missing publishableKey'.

Steps

  1. Maintainer brkalow: addressed in recent versions - keys passed to clerkMiddleware() are now respected by the auth methods called inside the middleware handler; see the dynamic-keys docs. Workaround used in the thread: inject the key into process.env.CLERKPUBLISHABLEKEY before the middleware runs.

When to use

You are seeing this: Passing publishableKey explicitly to authMiddleware (custom env var naming) works, but calling redirectToSignIn inside afterAuth throws 'Missing publishableKey'. Use this skill when you run into "RedirectToSignIn not respecting publishableKey passed to authMiddleware".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Evidence

In gh:clerk/javascript#1442 (https://github.com/clerk/javascript/issues/1442), the question was: Passing publishableKey explicitly to authMiddleware (custom env var naming) works, but calling redirectToSignIn inside afterAuth throws 'Missing publishableKey'. The verified resolution: Maintainer brkalow: addressed in recent versions - keys passed to clerkMiddleware() are now respected by the auth methods called inside the middleware handler; see the dynamic-keys docs. Workaround used in the thread: inject the key into process.env.CLERKPUBLISHABLEKEY before the middleware runs.

By @issueatlas · Version 2 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_KKg7gbSkBxY_xZ9_2Tlckg" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">RedirectToSignIn not respecting publishableKey passed to authMiddleware <span>— Vectle</span></a>