[msal-node] Support updating the client assertion after creating the confidential client
See original GitHub issueCore Library
MSAL Node (@azure/msal-node)
Wrapper Library
Not Applicable
Description
In MSAL for .NET, the confidential client class has a method confidnetialClient.WithClientAssertion()
which allows passing an asynchronous callback to update the client assertion.
The Azure SDK for JS&TS team would like to have this feature also in msal-node!
How does that sound? Feedback appreciated.
Source
Internal (Microsoft)
Issue Analytics
- State:
- Created 2 years ago
- Comments:7 (7 by maintainers)
Top Results From Across the Web
@azure/msal-node package | Microsoft Learn
clientAssertion - Assertion string that the application uses when requesting a token. Only used in confidential client applications. Assertion should be of type ......
Read more >Using certificate credentials with MSAL Node - GitHub
clientAssertion : a string that the application uses when requesting a token. The certificate used to sign the assertion should be set on...
Read more >ConfidentialClientApplication | microsoft-authentication ...
Defined in msal-node/src/client/ConfidentialClientApplication.ts:31. Constructor for the ConfidentialClientApplication. Required attributes in the ...
Read more >msal - Can I use acquireTokenByclientCredential using ...
To perform the app-only authentication, you need to use a client secret or a client assertion, which means that your client should be ......
Read more >Azure devops client credentials flow - Grande Pelle
Here I will go through how to generate a client assertion and get the ... 2.0 client credentials grant flow permits a web...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
A use case for this callback functionality is that you’re then able to generate an assertion in the key vault without being able to export the certificate. I’ve build a small extension for the dotnet SDK that dynamically creates an assertion on demand, by sending the unsigned assertion to the keyvault and signing it in the cloud.
more details here and here
Work item is created & added to backlog. As Jason said, can’t comment yet on priority. CC @sameerag