-
Notifications
You must be signed in to change notification settings - Fork 59
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
Retrieve access token from AAD B2C #709
Comments
Same here! |
@anthonychu @simonaco @mkarmark @miwebst Can someone please address the issue? |
Same issue here. React SPA App @jon-a-nygaard , did you find a workaround or go custom MSAL based approach? |
We went with custom MSAL instead of the built in integration |
Is your feature request related to a problem? Please describe.
I am using custom authentication with AAD B2C, and would like to retrieve the access token without using a second authentication request, and then use the token as authentication towards an API.
Describe the solution you'd like
I noticed a similar issue #591 where there's a request for supporting a hydbrid flow. It seems that the response type is hard coded, and if I was able to define the response type I imagine that I would be able to retrieve the access token in a
GetRoles
function as a workaround, similar to whats mentioned at #429 (comment).Preferably it would be great if the access token was automatically added to API function request headers, similarly to a token store as mentioned in #483. Alternatively I would like the token to be set on the client principle as another way to access it.
Describe alternatives you've considered
response_type
inloginParameterNames
to retrieve the access token, but with no luck as it appears it is hard coded.GetRoles
function as described in Create a function for assigning roles, but it does not seem to be included in my case.Currently it seems that my best approach is to use custom authentication with MSAL.js to handle this scenario.
Any possible solution or tips on workarounds is greatly appreciated.
The text was updated successfully, but these errors were encountered: