{{ message }}
Repository navigation
Commit 8259d5f
feat(backend): add secondFactorVerification to createSignInToken
A user with a second factor enabled who signs in with a sign-in token
still has to complete their second factor. Some customers who issue
these tokens from their backend want them to complete the sign-in
without that prompt. The Backend API
now accepts `second_factor_verification` on sign-in token creation
(clerk/clerk_go#23112): `fresh` treats the second factor as verified at
sign-in, and `stale` treats it as unverified, so a reverification that
requires a second factor still prompts for one. When it is set,
`expires_in_seconds` defaults to 10 minutes.
This exposes it as `secondFactorVerification` on `createSignInToken()`, and
makes `expiresInSeconds` optional, matching the API.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>1 parent 3068fe9 commit 8259d5f
3 files changed
Lines changed: 41 additions & 2 deletions
File tree
- .changeset
- packages/backend/src/api
- __tests__
- endpoints
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
43 | 43 | | |
44 | 44 | | |
45 | 45 | | |
| 46 | + | |
| 47 | + | |
| 48 | + | |
| 49 | + | |
| 50 | + | |
| 51 | + | |
| 52 | + | |
| 53 | + | |
| 54 | + | |
| 55 | + | |
| 56 | + | |
| 57 | + | |
| 58 | + | |
| 59 | + | |
| 60 | + | |
| 61 | + | |
| 62 | + | |
| 63 | + | |
| 64 | + | |
| 65 | + | |
| 66 | + | |
| 67 | + | |
| 68 | + | |
| 69 | + | |
| 70 | + | |
| 71 | + | |
| 72 | + | |
| 73 | + | |
| 74 | + | |
| 75 | + | |
| 76 | + | |
| 77 | + | |
46 | 78 | | |

0 commit comments