-
Notifications
You must be signed in to change notification settings - Fork 208
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] Token Acquisition Extensibility support #2975
Labels
Comments
bgavrilMS
added
enhancement
New feature or request
feature request
untriaged
needs attention
and removed
untriaged
needs attention
labels
Aug 12, 2024
for 3) (The constructor of TokenAcquisition in IdWeb looks for a TokenAcquisitionAddI) using the locator pattern (serviceProvider.GetService() |
bgavrilMS
added a commit
to AzureAD/microsoft-identity-abstractions-for-dotnet
that referenced
this issue
Aug 12, 2024
jennyf19
added
✏️design proposal
and removed
enhancement
New feature or request
feature request
labels
Aug 12, 2024
jmprieur
added a commit
to AzureAD/microsoft-identity-abstractions-for-dotnet
that referenced
this issue
Sep 18, 2024
* Support for token acquisition 1p features - AzureAD/microsoft-identity-web#2975 * Update public API files and version * Improving test coverage * Fix build on Linux (file casing) --------- Co-authored-by: Jean-Marc Prieur <jmprieur@microsoft.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What
This feature request proposes a mechanism to deliver token acquisition features that are 1p. The reason for this is twofold:
DownstreamApi
, by not exposing features directly in MSALHow
MSAL
A strongly typed API and a strongly typed processing. For instance for the Federated User Identities, this is a new method, say:
ConfidentialClientApplication.AddAddIn<1pFeatureAddin>(), with this 1pFeatureAddin belonging to a 1P library, and that would implement methods or be a factory of classes that would implement these methods to:
• Extract the parameters from the extension method and store them in a bag
• Understand the parameters from the bag
• Append the body of the request
• Append the headers of the request
• Append the query string of the request
• Retrieve the info from the response
• Create exceptions for the particular request
• Cache the token (if there are particular things to do)
• Add to a bag in the AuthenticationResult (From which it would be queried by an extension method also part of the Add-In package)
• Change API ID
Note: design not finalized here, but an interface or callback will constitute the integration point. Incremental start - expose only what is necessary.
Id.Web
AcquireTokenOptions has a new public property
ExtraParameters: IDictionary<string, object>
+ associated support from config.MISE
Services.Add1pFeature();
For more details see here
The text was updated successfully, but these errors were encountered: