Skip to main content

Mobile certificates page

Pega Community logo

Note: The following content, referenced from Pega Community, is included here to help you better achieve the module learning objectives.

A certificate set stores all the keys and certificates that are necessary to build, run, and distribute iOS apps.

A complete iOS certificate set consists of the following elements:
  • Bundle ID
  • Signing certificate
  • Mobile provisioning file
  • Push notification certificate

You can acquire the components for an iOS certificate set with an Apple developer account. Depending on your business needs, your organization must enroll in either Apple Developer Program or Apple Developer Enterprise Program. For example, if your organization plans to distribute iOS apps on the App Store, use an Apple Developer Program account. If your organization focuses on internal distribution, consider using an Apple Developer Enterprise Program account. For more information about enrollment options in the Apple Developer Portal, see the Apple developer documentation.

Note: Restrictive company policies might not allow developers to upload the company's signing certificates and provisioning profiles. If you want to export an unsigned mobile app and then sign it locally, you can create an unsigned certificate set that only uses the App ID and an optional push notification certificate. For more information, see Creating an unsigned iOS certificate set.
Bundle ID
A unique string that identifies an iOS app. The value of the bundle ID is case-sensitive and must meet the following requirements:
  • Consists of alphanumeric characters (a-z, A-Z, 0-9) or a hyphen ( - ).
  • Consists of at least two segments; all segments must start with a letter and be separated by a period ( . ).

For example: com.example.my.ios-app

The bundle ID is referenced in an App ID that links one or more apps from a specific development team. An App ID consists of a Team ID string that Apple generates for your development team, and a bundle ID search string that corresponds to the bundle ID of a specific app or a set of apps. The App ID also determines what types of iOS services your app supports.

Signing certificate
A certificate for digitally signing entries that identifies the developer of the iOS app and ensures that the app code comes from a legitimate source. You generate the signing certificate in the Apple Developer Portal to install the app on test devices and distribute the app with the Enterprise program or the App Store. You upload the certificate as a .p12 file to an iOS certificate set on Pega Platform.
Mobile provisioning file
A set of digital entities that acts as a link between the developer account and mobile devices. The provisioning profile is deployed in the app bundle and enables you to install and run the app for testing and distribution. In the Apple Developer Portal, you can create different types of provisioning profiles. For example, you can create a profile only for testing your app during development, or create a profile that allows you to publish your app on the App Store.
Push notification certificate
A certificate that Pega Platform server uses to communicate with Apple Push Notification service (APNs) and enable push notification support in your iOS app. You upload the certificate as a .p12 file to an iOS certificate set on Pega Platform.Note: The mobile provisioning file that you use in the certificate set must support push notifications. Otherwise, the push notification certificate section is not available in the Pega Platform certificate set.

What to do next: Obtain the components for an iOS certificate set by completing the following tasks:

  1. Obtaining an App ID for iOS apps

    Create a unique App ID in the Apple Developer Portal for the iOS certificate set that is required to generate an installation package for your iOS app.

  2. Obtaining a signing certificate for iOS apps

    Create a signing certificate for the iOS certificate set that is required to generate an installation package for your iOS app.

  3. Obtaining a mobile provisioning profile for iOS apps

    Create a mobile provisioning profile for the iOS certificate set that is required to generate an installation package for your iOS app.

  4. Creating an iOS certificate set

    Ensure that you can successfully generate an installation package with a signed iOS app by creating an iOS certificate set. With a certificate set, you provide components that control how you distribute your app to users and that determine what services are available. For example, you can create a certificate set that enables support for features such as push notifications.

  5. Signing iOS apps locally

    Follow your company policies and ensure that you do not expose your iOS certificates and provisioning profiles in third-party platforms, by signing your iOS apps locally.

Pega Community logo

Note: The following content, referenced from Pega Community, is included here to help you better achieve the module learning objectives.

A certificate set stores all the keys and certificates that are necessary to build, run, and distribute Android apps.

A complete Android certificate set consists of the following elements:
  • App ID (Package Name)
  • Signing certificate
  • Firebase Cloud Messaging (FCM) server key
  • Google Services JSON
App ID (Package Name)
A unique string that identifies an Android app on mobile devices and Google Play. The value of the App ID is case-sensitive and must meet the following requirements:
  • Consists of alphanumeric characters (a-z, A-Z, 0-9) or an underscore ( _ ).
  • Consists of at least two segments; all segments must start with a letter and be separated by a period ( . ).
For example: com.example.my.android_app
Signing certificate
A certificate for digitally signing entries, such as installer packages or emails. Android requires that all apps be digitally signed with a certificate before app installation. Android uses the certificate to identify the author of the app to ensure, for example, that the app updates come from an authentic source. The certificate does not have to be signed by a certificate authority.

You add a signing certificate to your Android certificate set by uploading a .p12 file with a single private key and a single certificate generated for signing.

FCM server key
A key that the Pega Platform server uses to authenticate with the FCM services. You can use this key to enable push notifications in an Android app.
Google Services JSON
A JSON configuration file for FCM-based projects. You can download this JSON file from the Firebase console and use it to enable push notifications in an Android app.

Tip: When you publish the app on Google Play, you should continue using the same App ID and signing certificate for the lifespan of the app. This approach ensures the possibility of future upgrades to your app.

What to do next: Obtain the components for an Android certificate set by completing the following tasks:

  1. Obtaining a signing certificate for Android apps

    Guarantee that the code and updates of your mobile app come from a legitimate source by creating a signing certificate for the Android certificate set that is required to generate an installation package for your Android app.

  2. Creating an Android certificate set

    Ensure that you can successfully generate an installation package with a signed Android app by creating an Android certificate set. With a certificate set, you provide the components which prove that the app code and updates come from an authentic source, and that also enable support for optional push notifications for your app.

If you are having problems with your training, please review the Pega Academy Support FAQs.

Did you find this content helpful?

Yes
No

Want to help us improve this content?
Suggest an edit

We'd prefer it if you saw us at our best.

Pega Academy has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice