useSignIn() and useSignUp() now handle Clerk Protect challenges
Custom flows using useSignIn() and useSignUp() now automatically handle Clerk Protect challenges by displaying them in a modal and returning once the user passes verification. For SSO flows, challenges appear when the user returns to HandleSSOCallback. Classic resource methods and apps without Clerk UI continue to return with 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 -
Updated dependencies [
c8eb8d5]:- @clerk/shared@4.37.1
Source: original entry ↗
More from Clerk
Follow Clerk to get its new changes in your feed and email digest.
Export HandleSSOCallback component from @clerk/nextjs
The HandleSSOCallback component is now exported from @clerk/nextjs, enabling its use on SSO callback routes in custom authentication flows. Previously the import would fail.
Add revokeCurrentDeviceCredential() to useBiometricCredentials()
A new revokeCurrentDeviceCredential() method has been added to useBiometricCredentials() for Expo, allowing you to revoke the device's biometric credential without storing the credential ID from enroll(). Call it before signing out since it requires an active session.
@clerk/nuxt@3.1.11
Patch release updating internal dependencies for @clerk/shared, @clerk/backend, and @clerk/vue to their latest versions.