Shulou(Shulou.com)06/02 Report--

This article will explain in detail how to solve the problems encountered in the distribution of ios applications within the enterprise. The content of the article is of high quality, so the editor will share it with you for reference. I hope you will have a certain understanding of the relevant knowledge after reading this article.

problem

Recently, we encountered the problem that neither the plist file nor the ipa file could be downloaded and installed when distributing iOS software within the enterprise. Install Apple's official documentation: "distribute internal applications through a web server". Set up a service to download the iOS installation package for employees within the enterprise. Recently, however, strong authentication has been added to the static resource file server that requires users to enter usernames and passwords in order to download files, which directly results in plist files and ipa being unable to download.

Reason

By grabbing the package, it is found that when the user clicks the download, that is, when he clicks the following code:

Install App

The Get request of the itms-services protocol to download the plist file does not carry the cookie logged in by the user, which causes the download to fail.

Reference solution

According to the "How to secure iOS enterprise distribution using oauth on a public facing website?" post, the idea is to make the two Get requests for downloading plist files and ipa files as separate services, as follows:

Summary

The problem of itms-services download should be solved by OAuth3. Specifically, you should take a look at several articles by Ruan Yifeng about OAuth3.0:

Understanding OAuth 2.0

A simple explanation of OAuth 2.0

Four ways of OAuth 2.0

It is best to use OAuth3.0 's authorization code mode to solve this. The OAuth3.0 flow chart is as follows:

In the authorization code mode, the OAuth3.0 authorization code is exposed only once at the front end, and the backend uses the authorization code obtained from the front end to obtain the access token, which ensures that the access token is always in the background. The next time the user requests, we can query the access token from the database according to the user, and invoke the third-party resource server by ourselves through the access token.

On the network, there is another flow chart of the authorization code model, which is more concise:

On how to solve the problems encountered in the internal distribution of ios applications to share here, I hope that the above content can be of some help to you, can learn more knowledge. If you think the article is good, you can share it for more people to see.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.