This repository has been archived by the owner on Aug 28, 2023. It is now read-only.
Support client_asserton for OIDC auth flow #231
Assignees
Labels
Comments
|
@lovemaths Thank you for the help for the other 3 feature requests. Hope you can help with this as well! |
lovemaths
added a commit
that referenced
this issue
Dec 23, 2016
lovemaths
added a commit
that referenced
this issue
Jan 3, 2017
lovemaths
added a commit
that referenced
this issue
Jan 4, 2017
For hybrid/code flow, client secret or client assertion is required to redeem the authorization code for access token. This fix enables user to use client assertion. 1. Added `thumbprint` and `privatePEMKey` options, so user can use the client assertion flow. However, client secret flow takes precedence. We will use client secret flow if `clientSecret` option is provided by user, regardless the values of `thumbprint` and `privatePEMKey`. 2. Added unit tests and end to end tests for client assertion flow.
lovemaths
added a commit
that referenced
this issue
Jan 6, 2017
Issue #231 Support client_assertion for OIDC auth flow
|
@Huan9 We added this feature in release 3.0.4. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
We are using microsoft first party app as our AAD app to do auth. For all the first party app, we cannot use client_key to get access token, we are forced to use client assertion to get access tokens from Azure AD. => without support for client_assertion, our subscription linking scenario will get blocked.
More detail has been described here:
https://azure.microsoft.com/en-us/documentation/articles/guidance-multitenant-identity-client-assertion/
So basically, it will be ideal, if we can pass in our private key in the config and the library can help to generate the singed JWT client_assertion when doing the token exchange process.
P.S. Search
client_assertionin below blogs, I think it help to understand how the flow works:http://www.dushyantgill.com/blog/2015/05/23/developers-guide-to-auth-with-azure-resource-manager-api/
http://www.andrewconnell.com/blog/user-app-app-only-permissions-client-credentials-grant-flow-in-azure-ad-office-365-apis
The text was updated successfully, but these errors were encountered: