[Cloudflare One] Clarify AAGUID/AMR incompatibility in independent MFA docs#30805
Open
kennyj42 wants to merge 2 commits into
Open
[Cloudflare One] Clarify AAGUID/AMR incompatibility in independent MFA docs#30805kennyj42 wants to merge 2 commits into
kennyj42 wants to merge 2 commits into
Conversation
- AAGUID restrictions and AMR matching CAN coexist (not mutually exclusive) - AMR matching is more permissive: IdPs don't include AAGUID in AMR claims - Remove Apple iCloud Keychain from no-AAGUID list (they do have AAGUIDs) - Remove AAGUID bullet from 'When AMR matching is skipped' section
sha-e-512
reviewed
May 13, 2026
|
|
||
| :::note | ||
| AAGUID requirements and [AMR matching](#use-identity-provider-mfa) cannot both be turned on at the organization level. If AAGUID requirements are turned on, Access skips AMR matching even when the identity provider returns a matching AMR value. | ||
| AAGUID restrictions and [AMR matching](#use-identity-provider-mfa) can both be turned on, but AMR matching is more permissive than independent MFA when AAGUID restrictions are configured. Most identity providers do not include AAGUID information in their AMR claims, so Access cannot verify that the authenticator used for IdP MFA is in the list of approved AAGUIDs. If the IdP returns a matching AMR value, Access will skip the independent MFA prompt regardless of which authenticator the user used at the IdP. |
There was a problem hiding this comment.
nit: 'can both be turned on simultaneously'.
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
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.
Summary
Moves the AAGUID/AMR incompatibility explanation from the
When AMR matching is skippedbullet list into the AAGUID section's existing note block.Before: The
When AMR matching is skippedsection had a bullet explaining that AAGUID info isn't in AMR claims. This duplicated context and buried the explanation away from where admins configure AAGUID restrictions.After:
When AMR matching is skippedsection no longer mentions AAGUID (the note in the AAGUID section already covers this).