-
Notifications
You must be signed in to change notification settings - Fork 145
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
retrieving token with multiple scopes (including delegated permission) not working #1275
Comments
@thomas-topway-it: do you have the same error as in #865? In case you have a different error, could you please share its detail? |
@hieunguyenmsft I will send you the log as soon as possible, currently
both on ios and android, but indeed I need to retrieve the log and to ensure the http request is precisely the same, because, in the same flutter app, the flow seems to behave differently. I already proposed the following somewhere else, but don't you think it would be worth for your team to contribute to a reliable flutter plugin for msal, given that the current libraries are poorly maintained or not maintained at all, and the growing interest for flutter ? I think most of the issues depend from the libraries rather than to msal itself (but, please, don't put yet the "external" label to this thread) and that negatively impact the msal library as well |
Supporting for a new language is great as it can bring MSAL to more people, but in another hand our resource is limited, and we don't have experience with Flutter. I will forward the ask to my manager to see what we can do with it. |
Please reopen once you get logs. |
Hi, Could you assist with that? Thanks |
Sure @hkozlovskyi I'm happy to help. Could you please clarify your current setup:
|
Hi @hieunguyenmsft
`MSAL log: TID=2529955 MSAL 1.1.17 iOS 14.5.1 [2021-05-12 20:47:21] Requiring default broker type due to app being built with iOS 13 SDK
Error: Cannot acquire token` |
Hi @hkozlovskyi, I checked with our server team and the problem is in the scope content {email, "api:///access_as_user"}. |
Hi @hieunguyenmsft Thank you! |
As far as I know, there is no workaround for that. I'm not sure if server has the plan to support multiple audiences from one token in the future. If any news, I will update you via this ticket :) |
@hkozlovskyi Maybe you can add email as an optional scope to idToken : https://docs.microsoft.com/en-us/azure/active-directory/develop/active-directory-optional-claims#configuring-optional-claims |
@hieunguyenmsft thanks for your help. @ameyapat will try, thank you! |
Hello I'm trying to retrieve a token using delegated permission, like this
and it works, but when I use the following
it does not work. I have also tried the following
assigning all the related scopes to the "authorized client application"
but it does not work either.
I have found the following ticket
#865
which indicates a workaround about that, but I'm not sure it is applicable to the new version of the portal.
How can I solve that with the new version of the portal ? (*** the issue also occurs using msal 1.1.15)
thanks
(Thomas)
The text was updated successfully, but these errors were encountered: