Skip to content
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

Closed
jennyf19 opened this issue Aug 26, 2019 · 5 comments
Closed

Part 1: Modify iOS broker to handle iOS 13 changes #1357

jennyf19 opened this issue Aug 26, 2019 · 5 comments

Comments

@jennyf19
Copy link
Collaborator

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.

@bgavrilMS
Copy link
Member

What is the user impact?

@jennyf19
Copy link
Collaborator Author

@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.

@bgavrilMS
Copy link
Member

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.

@henrik-me
Copy link
Contributor

@jennyf19 : I created a new issue to track part 2 as this issue is linked to the 4.4.0 release.
Part2: #1396

@henrik-me henrik-me changed the title Modify iOS broker to handle iOS 13 changes Part 1: Modify iOS broker to handle iOS 13 changes Sep 21, 2019
@henrik-me
Copy link
Contributor

Cloned the issue to fix the rest in the next release

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants