Update disable-user-mfa.mdx with Client Trust warning #2829
+3
−0
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Added a warning about the introduction of Client Trust and its impact on MFA enforcement.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
|
Merged main to fix the build as the Client trust PR was merged yesterday. So this is good to go I think. @mtliendo |
SarahSoutoul
approved these changes
Nov 27, 2025
manovotny
reviewed
Dec 1, 2025
| {/* clerk/javascript file: https://github.com/clerk/javascript/blob/main/packages/backend/src/api/endpoints/UserApi.ts#L206 */} | ||
|
|
||
| > [!WARNING] | ||
| > On November 14, 2025, Clerk introduced **[Client Trust](/docs/guides/secure/client-trust)**. This free security protection automatically enforces MFA **the first time** a user logs in from a new device even if MFA is disabled. Learn more about Client Trust and our commitment to security by [visiting our changelog](https://clerk.com/changelog/2025-11-14-client-trust-credential-stuffing-killer). |
Contributor
There was a problem hiding this comment.
- Removed domain from URL
- Removed "by visiting our changelog" (optional)
Suggested change
| > On November 14, 2025, Clerk introduced **[Client Trust](/docs/guides/secure/client-trust)**. This free security protection automatically enforces MFA **the first time** a user logs in from a new device even if MFA is disabled. Learn more about Client Trust and our commitment to security by [visiting our changelog](https://clerk.com/changelog/2025-11-14-client-trust-credential-stuffing-killer). | |
| > On November 14, 2025, Clerk introduced [**Client Trust**](/docs/guides/secure/client-trust). This free security protection automatically enforces MFA **the first time** a user logs in from a new device even if MFA is disabled. Learn more about [Client Trust and our commitment to security](/changelog/2025-11-14-client-trust-credential-stuffing-killer). |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Added a warning about the introduction of Client Trust and its impact on MFA enforcement.
🔎 Previews:
What does this solve?
Seeing an uptick in seeing an uptick in mfa related questions since launching client trust since launching Client Trust
What changed?
Checklist