Skip to content
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

[Feature Request] Expose client capabilities in AssertionRequestOptions for MSI FIC scenarios #4948

Open
gladjohn opened this issue Oct 1, 2024 · 3 comments · May be fixed by #4972
Open

Comments

@gladjohn
Copy link
Contributor

gladjohn commented Oct 1, 2024

MSAL client type

Managed identity

Problem statement

Update AssertionRequestOptions to handle client capabilities for MSI Federated Identity Credential (FIC) scenarios, ensuring that higher-level SDKs can pass capabilities to MSAL.

Proposed solution

We will introduce a new property ClientCapabilities in the AssertionRequestOptions class to support the passing of capabilities during token acquisition.

Alternatives

No response

@gladjohn gladjohn added untriaged Do not delete. Needed for Automation needs attention Delete label after triage scenario:ManagedIdentity and removed untriaged Do not delete. Needed for Automation labels Oct 1, 2024
@gladjohn gladjohn added this to the 4.65.0 milestone Oct 1, 2024
@gladjohn gladjohn self-assigned this Oct 1, 2024
@gladjohn gladjohn added Feature Request and removed needs attention Delete label after triage labels Oct 1, 2024
@bgavrilMS
Copy link
Member

Is this needed ? If the app declares client capabilities, then they should simply apply to both the assertion provider and to the CCA object.

@bgavrilMS
Copy link
Member

Thinking more about this, it is ok to add to help create the assertion.

@gladjohn
Copy link
Contributor Author

moving to in-progress @bgavrilMS based on our discussion @localden FYI

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment