New POP test - Sni Assertion Flow Uses JwtPop And Succeeds #5667
+100
−0
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.
This pull request adds a new integration test to validate the client assertion flow with JWT PoP (Proof of Possession) binding in the
ClientCredentialsMtlsPopTestsclass. The new test ensures that MSAL correctly uses thejwt-popclient assertion type when a binding certificate is supplied and PoP is enabled. Additional minor improvements include new constant definitions and using extra namespaces.New test for JWT PoP client assertion flow
Sni_AssertionFlow_Uses_JwtPop_And_Succeeds_TestAsync()to verify that MSAL uses thejwt-popclient assertion type and includes the correct body parameters when acquiring tokens with mTLS PoP and a client assertion. The test also checks the correct invocation of the assertion provider and validates the returned access token and scopes.Test setup improvements
TokenExchangeUrlfor use in token acquisition flows.Namespace and dependency updates
System.Linq,System.Threading, andMicrosoft.Identity.Client.Extensibilitynamespaces to support new test logic and features.