Enterprise Certificate ($299) in-house way of publishing guide

One, clear several concepts

1, Enterprise version IDP: that is, iOS Development Enterprise program. Attention is the $299/year kind, not the $99/year kind.

2, in house: is only the internal release of enterprises, only the use of internal personnel.

Second, in-house mode characteristics 1, can not be published to the Apple Store for sale. 2, do not need Apple review. 3, you can use any known private APIs. 4, can be installed on any Apple equipment, without any signature and certification. 5, the user installs only needs one IPA file, does not need the certificate and the signature document.
Third, the certificate generation process 1, Generate development and release certificate (CER file), and $99 account. 2, create app ID, same as $99 account. 3, create and develop mobileprovision files, and the same as $99 account. 4, create the release (in-house) mobileprovision file, the following figure and $99 account is different.   Ad hoc is published in the same way as $99, where we chose to house. 5, the newly generated certificate and signature files are installed, you can start our release.
Four, in-house packing here take XCODE5 for example, different versions may have subtle differences. 1, the project configuration, and just installed the certificate file association. 2, configure Archive options: 3, archive:product----> Archive 4, after the completion of the compilation, pop-up packaging page. The following figure: 5, click "Next" to continue, the following figure:
6, fill out the information, click Save, Open the folder we selected above, will see the following 2 files: 7, the release of the packaging work completed.
Five, Enterprise Web server distribution
1, put the packaged files on the enterprise server, IOS devices by visiting the corporate Web site, download the installation directly. 2, one-click installation implementation: 1, the Site page to add a label. 2, the corresponding link to the label is as follows:

<a href= "Itms-services://?action=download-manifest&url=http://url/hello.plist" >Hello</a>
Six, iOS equipment, open the website page, click on the tag, pop-up installation prompts, continue.

Original

Problem:

Users who have been upgraded to iOS7.1 in recent days may find that an enterprise application that could have previously been installed could suddenly fail to install, prompting questions such as "the application cannot be installed because the HTTP://XXX.XXX.XXX certificate is invalid".

Reason:

For the new 7.1 system to install the enterprise application, the URL must be HTTPS, not HTTP, which means our server will support HTTPS.

Workaround:

To embed a link in the original page:

Itms-services://?action=download-manifest&url=http://www.test.com/manifest.plist

To

Itms-services://?action=download-manifest&url=https://www.test.com/manifest.plist

Can. Note: You need to increase the server's support for HTTPS, otherwise you will be prompted not to link to the Web site.