Push Notification Configuration

In order for Ostetso to deliver push notifications to your apps there is some required setup must be done on the Apple Developer Member Center. From there you will generate certificate files that will be downloaded to your local machine and then uploaded to the Ostetso App Configuration page as part of your Ostetso setup.

Since Ostetso handles the more complex part of sending out push notifications and handling them in your apps, you don't need to become an expert on the intricacies of how to implement them and you should just be able to follow the simple steps listed below. However, if you would like more details you can read about iOS push notifications here.

Push setup is relatively straight forward and can be accomplished by following these steps:

  1. Go to https://developer.apple.com/membercenter and login to your developer account. (And while we can’t swear to this, anecdotal evidence seems to indicate that the developer portal behaves much better if you’re visiting via Safari, vs other browsers).
  2. Select the "Certificates, Identifiers & Profiles" link.
  3. Select "Identifiers" under "iOS Apps".
  4. Select the app that you are going to use with Ostetso
  5. You will see a list of all of the Application Services available for your app including Push Notifications. Select the "Edit" button at the bottom of this list.
  6. Make sure that the check box to the left of "Push Notifications" is selected.
  7. You will see two SSL Certificate types listed under Push Notifications. You will need to generate both of these certificates for use with Ostetso. The Development Certificate will be for testing in the sandbox environment of Ostetso and the Production Certificate will be used by your live app in the production environment. We’ll start with the Development Certificate, so in the "Development SSL Certificate" section select "Create Certificate."

  8. Follow the instructions exactly as provided on the Apple web site for creating a Certificate Signing Request, which will involve using the Keychain Access app on your Mac to generate a CSR file and save it to your local hard drive (probably with filename CertificateSigningRequest.certSigningRequest).
  9. Return to the Apple web page, click ‘Continue’ and then follow the instructions provided to ‘Generate your certificate’. This will involve uploading the CSR file you generated in the previous step and clicking on the ‘Generate’ button. You should end up with a page that says ‘Your certificate is ready’.
  10. From here you can now download the generated certificate file (default name will be aps_development.cer). This file is not exactly the format that we need yet so there's still some work to do. Double click on the file that you just downloaded, which will add the certificate to your keychain.
  11. Open the Keychain Access application on your Mac and find the newly added file. You’ll probably need to have the ‘login’ Keychain selected, as well as the “Certificates” Category. The new certificate should be named something like Apple Development IOS Push Services: and then something specific to your app.
  12. Expand the certificate entry in the keychain so that you see both the certificate and the private key. Select both of these items and right click, which displays a popup menu. Select "Export 2 items."
  13. Leave the file format menu on the default setting of "Personal Information Exchange (.p12)" and save the file to your local disk.
  14. A window will pop up asking you to set a password. Leave the password blank and select "OK". You may be asked for the password for your keychain as well.
  15. You now need to go to the command line terminal and cd into the directory where you saved the .p12 file.
  16. We need to convert the .p12 file into a .pem file, so run the following command in the terminal (assuming that you kept the default file name Certificates.p12 when you exported above):
    openssl pkcs12 -in Certificates.p12 -out pushcertDevelopment.pem -nodes -clcerts
    Note: if you are creating the Production pem file, name it pushcertProduction.pem instead of pushcertDevelopment.pem.
  17. You may now delete your .p12 file.
  18. Repeat steps 7-17 for your Production SSL Certificate.

If everything’s gone smoothly you should now have 2 PEM files that you will upload to Ostetso on your App page where you are asked to upload your Push Token Certificates.