User Profile
JoshKBCCG
Copper Contributor
Joined 6 years ago
User Widgets
Recent Discussions
Re: MSIX automatic updates and authentication
Tanaka_Jimha Edit: made this a separate post. I'm wondering if this backlog item will solve my issue, which is I want to host the https://docs.microsoft.com/en-us/windows/msix/app-installer/installing-windows10-apps-web in an Azure web app behind Easy Auth so that only users in the linked Active Directory can access the installation download. Easy Auth works as expected to require login to the web page, but the App Installer experience fails with 'An error occurred while accessing the file from the web. Please try downloading and opening the file locally.' I'm guessing this same issue will impact the automatic update functionality of the UWP app as well. Curious if 'AppInstaller user authentication' would solve this problem, or if it will be an authentication experience after the MSIX package has already been downloaded.4.8KViews0likes0CommentsUWP web distribution behind AAD auth
I've https://stackoverflow.com/questions/63454137/uwp-side-loaded-app-distribution-from-aad-protected-web-site and also as a reply on another thread in this forum, but think this question is appropriate as a stand-alone topic in this forum. I have an internal LOB UWP app which I want to make available to company employees across the world. With the future of the MS Store for Business uncertain, we've move in the direction of web distribution. The app already does AAD auth internally, but we'd like to require users to be authenticated against AAD before even getting to the web distribution page. Pushing this out to an Azure web site with 'https://docs.microsoft.com/en-us/azure/app-service/overview-authentication-authorization' turned on seems like a good solution for this. However, turning this feature on breaks the installer experience with the AppInstaller displaying the message 'An error occurred while accessing the file from the web. Please try downloading and opening the file locally'. This is probably because the AppInstaller is making its own http request to the msix file without using inherited auth tokens from the original web login. My guess is this will also be a problem for the auto-update feature. Is this problem solvable today or will it be solvable in the future? Is there a better approach to this problem which doesn't require being on a company WAN?Solved1.7KViews2likes2Comments
Recent Blog Articles
No content to show