-
Notifications
You must be signed in to change notification settings - Fork 340
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Expose client capabilities in AssertionRequestOptions for MSI FIC scenarios #4972
base: main
Are you sure you want to change the base?
Conversation
/// <summary> | ||
/// Client Capabilities to be included in the client assertion | ||
/// </summary> | ||
public IEnumerable<string> ClientCapabilities { get; set; } |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Aren't going to set these?
@@ -1857,6 +1857,7 @@ public void AssertionInputIsMutable() | |||
options.TokenEndpoint = "https://login.microsoft.com/v2.0/token"; | |||
options.CancellationToken = CancellationToken.None; | |||
options.Claims = TestConstants.Claims; | |||
options.ClientCapabilities = TestConstants.ClientCapabilities; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A test for this is as follows:
- Create a CCA + WIthClientAssertion(AssertionOptions o => { Assert.AreEquals( "cp1", o.CP})
- Call AcquireToken*.WithCP("cp1");
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You also need to set them.
Fixes #4948
Changes proposed in this request
Updated AssertionRequestOptions to handle client capabilities for MSI Federated Identity Credential (FIC) scenarios, ensuring that higher-level SDKs can pass capabilities to MSAL.
Testing
unit tests
Performance impact
n/a
Documentation