Improvement4.37.1
Custom flows with useSignIn/useSignUp now handle Clerk Protect challenges
useSignIn() and useSignUp() custom flows now automatically handle Clerk Protect challenges by displaying them in a modal and returning once the user completes the challenge. SSO challenges appear at HandleSSOCallback, while classic resource methods continue returning protectCheck as before.
Patch Changes
- Custom flows built with
useSignIn()anduseSignUp()now handle Clerk Protect challenges for you. When a sign-in or sign-up method gets a challenge, Clerk shows it in a modal and the method returns once the user passes it. For SSO, the challenge appears when the user comes back to<HandleSSOCallback />. Classic resource methods such asclerk.client.signIn.create(), and apps without Clerk's UI loaded, still return withprotectCheckset, as before. (#9950) by @wobsoriano
authsecurityhooksssoclerk-protect
Source: original entry ↗
More from Clerk
Follow Clerk to get its new changes in your feed and email digest.
Improvement3.1.11
@clerk/nuxt@3.1.11
Patch release updating internal dependencies for @clerk/shared, @clerk/backend, and @clerk/vue to their latest versions.
nuxtdependenciespatch
Improvement1.39.1
@clerk/ui dependency updates
Updated @clerk/shared and @clerk/localizations dependencies to their latest patch versions.
dependenciesuilocalization
Improvement7.9.12
@clerk/nextjs 7.9.12
Patch release updating internal dependencies including @clerk/react, @clerk/shared, and @clerk/backend to their latest versions.
nextjsdependenciespatch