Cannot find private key for Apple Development Push Services

Question

I have consulted with many sources and still can not understand this.

http://code.google.com/p/apns-php/wiki/CertificateCreation

Basically, after I downloaded the SSL certificate for the development of the Push server from the iOS Provisioning Portal> App IDS (with the "Enable Apple Push Notification" service enabled), and I double-click on the certificate (file name aps_development.cer) to open it, Keychain will open. Then I select "login" and "Certificates" in the left panels. In the right pane, I see "Apple Development IOS Push Services: ...", and all the instructions that I have consulted so far have told me to "expand" this option by clicking the arrow next to the name to open the private key, but for This certificate does not have an extension option. Can someone help me find this private key? Did I upload the wrong certificate?

thank

Answer 1

My problem was that in the case of some, various certificates were added to the System keychain, and not to the "login".

Selecting "login" and then adding them with a small "+" (next to i), they were added to the right place.

Answer 2

I noticed that the extension icon actually appears when you click "My Certificates" in the menu on the left ("Keychain").

Answer 3

What I came across when I created the CSR file, I put the Common Name in a space. And the certificates created by this CSR file did not display the expand arrow in Keychain Access

After I created a new CDR file with a short common name and updated certificates, it installed well and has a private key.

Answer 4

on the machine to which you are trying to access this certificate, do you have a key with which you signed the certificate signing request (based on which the apple created this certificate for you)?

You should ask the person who created this certificate. This is probably the only way to get the secret key.

Answer 5

I had the same problem. Double-clicking on the .cer file placed the certificate in the keychain but did not display the private key (and this entry was not expanded).

I fixed the problem using the following steps:

• Disable keychain access.
• right-click the .cer file (e.g. aps_production.cer)
• Select "Open s> Access Key Fob (default)"

... and voila, now it appears with the private key. This is rather strange, since in any case it opens access to Keychain.

Answer 6

Grant access to the keychain and follow the steps below ...

Answer 7

Delete a certificate that does not have a private key. Open Keychain Login, then drag the file from Finder to Login and your certificate now has a private key!

Answer 8

I just double clicked on the certificate. As a result, it helped me to drag the certificate to the appropriate section.

More information can be found in this blog: How to export a Push Push certificate to a p12 file?

Answer 9

My problem was that I did not look at "Certificates", but in the "All Elements" section:

Answer 10

Leaving this here, hoping this helps someone with similar symptoms. When you click aps.cer to open it using Keychain Assistant, it will prompt you to select a dialog to import the certificate. For me, the private key did not appear in the folding key for any other key than login (that is, others such as System or System Roots seemed to display only the certificate).

Answer 11

Another answer to this question ...

After you create your CSR, before uploading it to the Apple website, you can look in Keychain Access under logins → and see that you already have new public and private keys with the same name as in the new CSR CommonName .

Therefore, when you upload the CSR to Apple, then upload the certificate, then double-click the certificate, access to Keychain simply matches that downloaded public key certificate, which was already on your Keychain Access list, and it attaches the private key.

So, if you can’t get the private key after all this, try to recreate your CSR.

The strange thing for me is that I read that you can use the same CSR every time you recreate your certificate, but for some reason this does not work for me. Perhaps due to the fact that the old deprecated certificate that I replaced was no longer in my key access list and therefore there was no public / private key pair that corresponded to the new generated certificate.

Answer 12

The .cer file does not contain a private key, only a public one. Thus, all these solutions are relevant only from the computer that issued the original CSR, or from the computer on which the original certificate key pair was imported into the keyring.

If you do not have access to the private key, you will need to generate a new certificate. However, you do not need to revoke the old certificate on the Apple Certificate Portal, as you can use multiple APNS certificates for the same application identifier.

Answer 13

Delete the certificate that does not have a private key. Open login in keychain

Drag these two certificates into the keychain

Wow, there is a private key in your keychain.