IOS certificate Request and usage details (detailed version)

For iOS developers, Apple developer accounts are certainly not unfamiliar. We can't do without it in development. Let me briefly share some of the knowledge about certificates used in iOS development.

The first part: introduction of Members 1. Certification (certificate)

Certificate is the qualification of computer development certification, each developer account has a set, divided into two kinds :

1) Developer Certification (development certificate)

Install on the PC to provide permissions: The developer tests the device for real-world testing.
Copies can be generated for multiple computers to be installed;

2) Distribution Certification (release certificate)

Install on your PC to provide permission to publish iOS programs: Developers can make beta and release programs. Cannot generate a copy, only the computer configured with the certificate can be used;

2.Provisioning Profile (authorization file)

Authorization files are authorizations for devices such as ipod Touch, IPad, iphone, the udid of the device and the app ID of the program, which allows the authorized device to install or debug the bundle identifier program that corresponds to the app ID recorded in the authorization file.
The developer account will choose the app ID when creating the authorization file (add the app ID in the developer account, select a single) and Udid (add up to 100, multi-select in the developer account under devices).
The authorization file is divided into two types, corresponding to the corresponding certificate use:

1) Developer Provisioning profile (Development authorization file)

When used on a computer with a development certificate or copy, the developer chooses the authorization file to install the program to a device in the authorization file record through the computer, which can be tested on the real machine.
Note: Make sure that the computer has permissions to debug, that is, the development certificate or copy is installed, the bundle identifier of the program in the development tool and the app ID of the selected authorization file are consistent; The udid of the device that connects the debugs is recorded in the selected authorization file.

2) Distribution Provisioning profile (Release authorization file)

The beta and release programs are made on the computer that has the certificate issued (that is, the computer that configures the certificate).
The release is the program file that is published to the App Store, and the developer account chooses the store option when creating the authorization file, choose the app Id, no need to select Udid;
The beta version is the program files that the tester can sync to the device before it is released, select Adhoc when creating the authorization file for the developer account, select the app ID and Udid, and only the selected Udid device may install the program that is made from that authorization file.

3. Keychain (Development key)

If the certificate is installed successfully under the certificate will generate keychain, the above mentioned certificate copy (export certificate renaming) is to configure the certificate of the computer to export keychain (that is. p12 file) installed on other machines, so that the other machine to get the certificate corresponding permissions. Developer certification can make copies keychain distributed to other computers to be installed so that they can be tested on the real machine.
Note: Distribution certification can only be used by computers that have a certificate configured, so even if the export export keychain is installed on another computer, it is not possible for other computers to have certificate permissions.

Part II: Certificate application process Step1: Login ($ 99 account) https://developer.apple.com
C_1.jpg

1) After successful login, select "Certificates" on the right side of the page:

C_2.png

2) After opening, you can see the panel:

C_3.PNGSTEP2: Generating a CSR file

1) Open Keychain Access

C_5.png

2) Open the top right keychain Access bar, certificate Assistant, request a certificate from a certification authority ...

C_4.png

3) Fill in an email address, select "Save to Disk", click Continue, complete.

C_6.png

Documents after successful application:

C_7.PNGSTEP3: Register APP ID Process

1) Click the plus sign in the top right corner of app IDs in the C_3 chart panel. Then fill in the name of the app ID:

C_8.png

2) Fill in the bundle ID:

C_9.png

3) Select the services that the app needs to support (e.g. app play push service, tick push notifications)

C_10.png

4) Finally there will be a detailed list of contents, corresponding to the correct, submit completed.

STEP4: Certificate Request

1) Select the type of certificate, the following list of our common iOS development certificate types

C_11.png

2) If you are applying for a push certificate, an app ID will be associated

C_12.png

3) Upload our previously built CSR file (see STEP2)

C_13.png

4) Congratulations, so far, you have completed the application of the certificate, simple.

SETP5: Authorization file Request (Provisioning profile)

1) Select the type of authorization file listed below for iOS frequently authorized file types

C_14.png

2) Select Affiliate app ID

C_15.png

3) Select the associated certificate

C_16.png

4) Select the authorized device (via UDID), except the Enterprise Certificate (inHouse), only the device you add can be scheduled or tested

C_17.png

5) Give the authorization file a name that can be distinguished from other authorization files

C_18.png

Congratulations, so far, the authorization file application is complete, simple.
In our iOS development, the common certificate-related operational processes are all on top.

Part III: summary

1) successfully installed the test certificate condition: a). Developer certificate + private key. b). authorization file.

2) If you want to perform a real-machine debug through a certificate, select the development certificate (development Certificate), and the appropriate authorization file (development Provisioning profile).

3) If you want more developers to be able to perform real-machine debugging, please authorize the device that requires real-machine debugging, then download the development certificate (development Certificate) to the native installation and export it to a private. p12 file, and the appropriate authorization file ( Development Provisioning Profile) is installed by the developer and is ready for real-machine commissioning after success.

4) If you want more machines to perform a real-machine test, first authorize the device you want to test, then select the production version certificate (distribution Ad_hoc Certificate) and the appropriate authorization file (distribution Ad_hoc Provisioning profile) is packaged and distributed to the device to be tested.

These are the records I use for iOS certificates in iOS development, and I hope it helps. Finally, thank you for browsing.

Wen/warrior_seven (author of Jane's book)
Original link: http://www.jianshu.com/p/01224fc523d4
Copyright belongs to the author, please contact the author to obtain authorization, and Mark "book author".

IOS certificate Request and usage details (detailed version)