Rebuild of IOS Push certificate

The push certificate for iOS is limited in duration and is typically one year. When our certificate expires, we need to regenerate the certificate. There was a period of time not on the Apple website, yesterday went up a look, this Austrian, revised, below we will regenerate a formal environment push push certificate.

1. First Open keychain (application-Utilities-keychain access), request a certificate

Common names are written as:2013.04.27_push_production_***. and saved to disk.

2. Go to the Certificate label page on the Apple website and select the app IDs sub-tab below the Identifiers tab to display the image below. In the red circle is the certificate that I want to regenerate the push signature. Click this certificate.

3. Certificate Details tab, Luo lists all the functional status, the final push notifications display can be configured, not enabled can state, so click the setting function to re-upload the certificate.

4. In the Certificate Settings page, the bottom push notifications as shown.

Where: Development SSL Certificate is the test environment certificate, Production SSL Certificate for the formal environment certificate, we generate a formal environment certificate, click on the back of Create Certificate.

5. The Create Certificate page is as follows. Click on the continue below.

6. Select the uploaded certificate, we have generated a certificate in the first step, upload this certificate.

7. After the upload is successful, the image below will be displayed. It is possible that the loading box will always be in the process of generating the certificate, and then re-enter this page. In fact, this time the certificate has been generated.

At this point, the push certificate has been generated and the expiration time is marked on the top, and the push certificate is valid for one year. Click Download to download this certificate.

8. Double-clicking the certificate that you just downloaded will automatically add the certificate to the keychain signature, as indicated in the red circle, as the certificate I just added, expand this certificate

Right-click Apple Production IOS pushservices:com.***.*** to pilot a. p12 file. Name is CERT.P12. In the export process will let the input and export password, enter the appropriate password.

9. Right-click on the 2012.04.27_push_producation_***, export a. p12 file, named Key.p12, the same as above in the export process will let the input export password, enter the appropriate password.

10. So far, we've got two. p12 files, put them under the same folder (AAA), you need to convert two. p12 files to a. pem file.

A. Open the terminal first, switch to folder AAA under Execute

[CPP]View Plaincopy

1. OpenSSL pkcs12-clcerts-nokeys-out cert.pem-in CERT.P12

At the time of execution, you will be prompted to enter a password and enter the password you just set to generate a Cert.pem file.

B. Re-execution:

[CPP]View Plaincopy

1. OpenSSL pkcs12-nocerts-out key.pem-in KEY.P12

At this point to note in the terminal prompt, the first time the password is generated when the certificate, the second time the third time to enter the password is the new password set KEY.PEM.

C. If you need to not encrypt key, execute the bottom statement

[CPP]View Plaincopy

1. OpenSSL rsa-in key.pem-out Key.unencrypted.pem

D. Then you can merge two . pem files , the Ck.pem is the certificate required by the server.

[CPP]View Plaincopy

1. Cat Cert.pem Key.unencrypted.pem > Ck.pem

At this point, the generated CK.PEM to the server-side personnel can.

Rebuild of IOS Push certificate