-
Notifications
You must be signed in to change notification settings - Fork 347
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
Part 1: Modify iOS broker to handle iOS 13 changes #1357
Comments
What is the user impact? |
@bgavrilMS iOS broker will not work. Based on the way we handle the sourceApplication and the call coming back from broker, we will have to modify how this is handled. Don't have all the details at the moment, but wanted to get an issue up so it's not forgotten about. |
Just trying to understand the impact here. So you mean that once people upgrade to iOS 13, pre-existing apps that use the broker will stop working? Sounds like a high priority item then. |
Cloned the issue to fix the rest in the next release |
iOS 13 has made changes around the authenticator's ability to verify applications. Currently, MSAL.NET relies on the sourceApplication to verify requests, this will need to be modified.
The text was updated successfully, but these errors were encountered: