Clarify claims challenge and client application roles#1917
Open
nlykkei wants to merge 1 commit intoMicrosoftDocs:mainfrom
Open
Clarify claims challenge and client application roles#1917nlykkei wants to merge 1 commit intoMicrosoftDocs:mainfrom
nlykkei wants to merge 1 commit intoMicrosoftDocs:mainfrom
Conversation
Contributor
|
@nlykkei : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
Contributor
|
Learn Build status updates of commit 4dc4102: ✅ Validation status: passed
For more details, please refer to the build report. |
kylemar
approved these changes
Mar 16, 2026
Contributor
There was a problem hiding this comment.
Pull request overview
Updates the introductory definitions in the Microsoft identity platform claims challenge article to better describe when claims challenges occur and who needs to handle them.
Changes:
- Refines the claims challenge definition to reference Conditional Access authentication context and session revocation scenarios.
- Rewords guidance about who must be prepared to handle claims challenges (from “Applications…” to “Clients of APIs…”).
| # Claims challenges, claims requests and client capabilities | ||
|
|
||
| A *claims challenge* is a response sent from an API indicating that an access token sent by a client application has insufficient claims. This can be because the token doesn't satisfy the Conditional Access policies set for that API, or the access token has been revoked. | ||
| A *claims challenge* is a response sent from an API indicating that an access token sent by a client application has insufficient claims. This can be because the token doesn't satisfy Conditional Access auth context values for that API, or the user's session has been revoked. |
| A *claims request* is made by the client application to redirect the user back to the identity provider to retrieve a new token with claims that satisfy the other requirements that weren't met. | ||
|
|
||
| Applications that use enhanced security features like [Continuous Access Evaluation (CAE)](~/identity/conditional-access/concept-continuous-access-evaluation.md) and [Conditional Access authentication context](https://techcommunity.microsoft.com/blog/identity/granular-conditional-access-for-sensitive-data-and-actions/1751775) must be prepared to handle claims challenges. | ||
| Clients of APIs that use enhanced security features like [Continuous Access Evaluation (CAE)](~/identity/conditional-access/concept-continuous-access-evaluation.md) and [Conditional Access authentication context](https://techcommunity.microsoft.com/blog/identity/granular-conditional-access-for-sensitive-data-and-actions/1751775) must be prepared to handle claims challenges. |
Contributor
|
Can you review the proposed changes? IMPORTANT: When the changes are ready for publication, adding a #label:"aq-pr-triaged" |
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.
No description provided.