[Bug] Missing Claims Propagation in SignedAssertionWithAssertionRequestOptions Delegate

[gladjohn]

Library version used

Latest

.NET version

net 8

Scenario

ConfidentialClient - service to service (AcquireTokenForClient)

Is this a new or an existing app?

This is a new app or experiment

Issue description and reproduction steps

When using the delegate-based flow (.WithClientAssertion(options => ...)) in MSAL to generate a client assertion, the Claims property from AssertionRequestOptions is not being propagated into the final assertion. Although Claims is already part of AssertionRequestOptions, it is currently not consumed or forwarded in code paths that rely on the delegate.

Relevant code snippets

Expected behavior

Claims provided in AssertionRequestOptions.Claims should be included in the client assertion that is sent to the token endpoint.

Identity provider

Microsoft Entra ID (Work and School accounts and Personal Microsoft accounts)

Regression

No response

Solution and workarounds

When building the AssertionRequestOptions, ensure that the Claims property is passed to the delegate and included in the final assertion.