You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a SPA frontend that login using MSAL with the authorization code flow with PKCE.
I have an API that needs to call the MicrosoftGraph API (downsteam) on behalf of the user. My API already require a valid Azure AD jwt token so my frontend already sends it to my API.
Why doesn't Microsoft.Identity.Web.MicrosoftGraph support header propagation of this auth token?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I have a SPA frontend that login using MSAL with the authorization code flow with PKCE.
I have an API that needs to call the MicrosoftGraph API (downsteam) on behalf of the user. My API already require a valid Azure AD jwt token so my frontend already sends it to my API.
Why doesn't
Microsoft.Identity.Web.MicrosoftGraphsupport header propagation of this auth token?Beta Was this translation helpful? Give feedback.
All reactions