Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Uploading a push notifications certificate

Updated on November 9, 2021

By uploading a push notifications certificate to an iOS certificate set in Pega Platform App Studio , you can use the certificate set for a mobile app that you are configuring, so that push notifications are enabled in the mobile app.

Before you begin: Before doing the steps in the following procedure, you must already have generated a .p12 file containing a single private key and a single public APNs certificate.
  1. Open an existing iOS certificate set.
    For more information, see Opening an existing iOS certificate set.
  2. From the Mobile Provisioning file list, click a provisioning profile that supports push notifications. Otherwise, the Push Notification Certificate list is not visible.
  3. Click New that is located next to the Push Notification Certificate list.
  4. Click Browse, and select an APNs certificate file from your directory that contains a single private key.
  5. In the Certificate name field, enter the name for the push notifications certificate. The name cannot include underscore ( _ ), hyphen (-), or period (.) characters.
  6. In the Encryption password field, enter the encryption password for the push notifications certificate.
  7. Click OK.
  8. Click Submit.
Result: After you upload a push notifications certificate for an existing certificate set, you can select this modified certificate set for your iOS mobile app. For more information, see Selecting an iOS certificate set.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us