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 signing certificate

Updated on November 9, 2021

You upload a signing certificate .p12 file from your local directory to a new or to an existing iOS certificate set. A signing certificate is used for digitally signing entries, such as installer packages, email messages, and similar items.

  1. If necessary, generate a new distribution signing certificate for your iOS app from the Apple Developer Portal and save it to your directory. For more information, see the Generating mobile certificates for the iOS platform Pega Community article.
  2. If the certificate set does not exist, create a new certificate set.
    For more information, see Creating an iOS certificate set.
  3. If the certificate set exists, open an existing certificate set.
    For more information, see Opening an existing iOS certificate set.
  4. Create an iOS certificate set.
    For more information, see Creating an iOS certificate set.
  5. Next to the Signing certificate field, click New.
  6. Click Browse, and select the signing certificate .p12 file from your directory.
  7. In the Certificate name field, enter the name for the certificate. The name cannot include underscore ( _ ), hyphen (-), or period (.) characters.
  8. In the Encryption password field, enter the encryption password for the certificate.
  9. Click OK.
  10. Click Submit.
Result: After you upload an iOS signing certificate for an existing certificate set, you can select this modified certificate set for your iOS custom 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.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us