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
{{ message }}
This repository has been archived by the owner on Nov 21, 2024. It is now read-only.
Since graph binding forces you to set the issuerURL in the AD Application that is assigned to the function, I am unable to find a way to support multitenancy.
Want I want is that any user from any tenant can call the api and be authenticated against their own Azure AD using delegated permissions. I have it working if I make the calls myself to get the token, but it would be nice if the binding could use the same issuer that was used to issue the authenticated user.
Perhaps i'm missing something, if so just tell me :D
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Since graph binding forces you to set the issuerURL in the AD Application that is assigned to the function, I am unable to find a way to support multitenancy.
Want I want is that any user from any tenant can call the api and be authenticated against their own Azure AD using delegated permissions. I have it working if I make the calls myself to get the token, but it would be nice if the binding could use the same issuer that was used to issue the authenticated user.
Perhaps i'm missing something, if so just tell me :D
The text was updated successfully, but these errors were encountered: