Page tree
Skip to end of metadata
Go to start of metadata


Some customers have multiple Apperian organizations and therefore a need to deploy multiple catalogs to the same user. For example, say that Company ABC has multiple corporate divisions, each with its own Apperian organization and branded App Catalog. Some Company ABC employees may work across divisions and need access to all the catalogs and the apps available through them.

Users can install multiple App Catalogs on the same device as long as the catalogs have separate bundle IDs (iOS) or package names (Android), which is the case when a user is installing App Catalogs built for different organizations.

Android App Catalogs are typically assigned the same package name by default. If you want to use multiple App Catalogs on Android, contact Customer Support to request a different package name.

To ensure that all Apperian features work properly with multiple catalogs, there are a few things to keep in mind. This page describes the requirements and considerations for running multiple App Catalogs on iOS and Android devices.

If you want users to be able to run multiple App Catalogs on the same iOS or Android device, follow these steps:

 
 

On This Page

Sign Apps with the Proper Credentials

In order for push notifications and application policies to work properly with multiple iOS App Catalogs:

  • Each of the iOS App Catalogs must be signed with a different provisioning profile that is associated with a unique explicit App ID. When creating the suffix for an App ID for an App Catalog, use appcatalog for the appname to ensure that the domain portion of the suffix is different. For example: 
    com.example.testorg.appcatalog and com.example.prodorg.appcatalog

    For instructions on creating a unique explicit App ID, see Manage App Identifiers.
      
  • The iOS App Catalog and each of the iOS apps in the same organization must be signed with credentials created using the same Apple account so that they share the same Team Identifier (Team ID). Apple uses the Team ID for the App ID prefix of an App ID. 
       
  • The SSL push certificate uploaded with each App Catalog must also be created using that same Apple account. For instructions on creating a push certificate, see Manage SSL Certificates for Push Notifications. For instructions on uploading a push certificate to Apperian, see Push Notification for an App Catalog.

Reapply Policies and Re-sign

For app policies to work properly with multiple iOS or Android App Catalogs, all apps with policies will need a new version of the policy layer. To get the latest policy layer, you must reapply policies and re-sign each app with policies, and then deploy the new versions as mandatory updates. 

To learn how, see Apply Policies to an App and Re-sign an App.


If you sign the app with Apperian, do not select the Enable app option when you sign it. You should enable the app on the Edit Application page and also mark it as a mandatory update.

  • No labels