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.

Android certificate set

Updated on November 9, 2021

A certificate set defines certain parameters of the mobile app for Android that you are creating.

For each certificate set, provide the following information:

  • App ID (Package Name) - A unique string that identifies an Android app that is under development. This value is case-sensitive and must start with an uppercase or a lowercase letter. You may use the underscore character ( _ ). At least one period (.) must be used to separate different parts. Example: com.example.my.android_app.
  • Signing certificate - A certificate that is used for signing entries, such as installer packages, email messages, and similar items. You must upload a signing certificate file that has been previously generated. Android requires that all apps be digitally signed with a certificate before they can be installed. Android uses this certificate to identify the author of the app, and the certificate does not need to be signed by a certificate authority. It must consist of a P12 file containing a single private key and a single certificate generated for signing.
  • FCM server key - A key that is used by the server to authenticate with the Firebase Cloud Messaging (FCM) services. Use this key to enable push notifications in an Android mobile app.
  • Google Services JSON - A JSON config file for a Firebase Cloud Messaging (FCM) based project. Use this JSON file to enable push notifications capability in an Android mobile app. Download the JSON config file from the Firebase console.
Note: By default, Java supports only certificate key sizes that are equal to or smaller than 1024 bits. If you need to use a larger key, you must update a .jar file in Java. For more information, see the Oracle Java documentation.
  • Opening a certificate set

    You open a new certificate set from the Channels and interfaces form for a mobile app, when the Android switch has been turned on. In this case, this new certificate set will be set up for the mobile app that you are configuring in the Pega Platform. You open a new certificate set from the Channels and Interfaces form for a mobile app, when the Android switch has been turned on. In this case, this new certificate set will be set up for the mobile app that you are configuring in App Studio.

  • Creating an Android certificate set

    To build a mobile app for the Android platform, you must create a certificate set in Pega Platform. App Studio. In order for the mobile app to use push notifications, you must also enable them in the app.

  • Uploading a signing certificate

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

  • Selecting an Android certificate set

    When you build your mobile app in the Pega Platform App Studio, you must create a certificate set, or, if one is already defined, select an existing certificate set for your Android mobile app.

Related articles

Generating installation packagesConfiguring push notifications for Android apps

Tags

Pega Platform 8.4 Mobile

Have a question? Get answers now.

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

Visit the Support Center

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.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us