**TL;DR:** Backend 401s only from some origins: a satellite domain, a preview deploy, or a native app. The token is genuine; its azp claim just is not on your allowlist. Confirm the cause 1. Decode the token payload without verifying and read the azp claim.

## The fix

1. Decode the token payload without verifying and read the `azp` claim. That is the origin that minted the token.

2. Compare it to the `authorizedParties` you pass to `verifyToken` / `authenticateRequest`. The failing origin is missing from the list.

3. Check whether you recently added a new frontend (satellite domain, new subdomain, native scheme) without updating the list.

4. Add every origin that legitimately mints tokens to `authorizedParties`: your web origin, satellite domains, and native app identifiers.

5. Do not "fix" this by dropping the check or widening it to everything. For cookie-based sessions this check is your CSRF protection.

## When to use this

- You are seeing this exact error message; match the block above, not just part of it.
- The failing call matches the scenario in the title: verifyToken rejects tokens from your own frontend.
- You want the fastest verified fix before digging through logs.

## When not to use this

- Your error text differs from the block above; close cousins often have different causes.
- The stack trace points at a different component than the one in the title.
- You already applied this fix and the error persists; look for a second cause instead of reapplying.

## Compatibility

- Not pinned to a specific version; follows current verifyToken behavior.