Мобильная версияMSAL/Azure B2c iOS — получение нового токена доступа с новыми областями ⇐ IOS
-
Гость
MSAL/Azure B2c iOS — получение нового токена доступа с новыми областями
In the documentation : https://learn.microsoft.com/en-us/azure ... -a-web-api it is stated:
If the access token's scope doesn't match the web API's scopes, the authentication library obtains a new access token with the correct scopes.
How is this token received from the iOS app's point of view? acquireTokenSilently is not called and I'm struggling to find any other resources that answers this.
Along with that question, if we have let's say 5 different backend services, all requiring new tokens with scopes, this will then in the app refresh the token a lot due to the complexity of our app. What's the approach here? Should in this case, 5 tokens be cached in the app? For me it sounds absurd.
Thank you in advance!
Источник: https://stackoverflow.com/questions/781 ... new-scopes
In the documentation : https://learn.microsoft.com/en-us/azure ... -a-web-api it is stated:
If the access token's scope doesn't match the web API's scopes, the authentication library obtains a new access token with the correct scopes.
How is this token received from the iOS app's point of view? acquireTokenSilently is not called and I'm struggling to find any other resources that answers this.
Along with that question, if we have let's say 5 different backend services, all requiring new tokens with scopes, this will then in the app refresh the token a lot due to the complexity of our app. What's the approach here? Should in this case, 5 tokens be cached in the app? For me it sounds absurd.
Thank you in advance!
Источник: https://stackoverflow.com/questions/781 ... new-scopes
