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 IDs (Android), which will be the case when a user is installing App Catalogs built for different organizations. 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

Ensure You Have the Correct Version of the App Catalog

For iOS, you need a version of the App Catalog released on or after September 15, 2015. For Android, you need a version of the App Catalog released on or after October 6, 2015. Push notifications and application policies will not work properly on devices running multiple App Catalogs that are not the correct version. 

If you have an older version of the App Catalog, contact Customer Support. They will rebuild your branded catalogs and upload them to each of your organizations. Customer Support can mark the new version of a catalog as a mandatory update to ensure that all users who already installed it will update to the latest version. To learn more about mandatory updates, see Update an Application.

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 applications 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 reapply policies and re-sign an app
  1. On the Applications page in the Apperian portal, click the Policies link next to the app to which you want to reapply policies.
  2. Click the Remove button to the right of the status message. When you click Remove, Apperian disables the app. You will re-enable it later in this procedure after you have re-signed it.
  3. Select the policies that you want to reapply to the app.
  4. Click Apply.
  5. When the "Pending Signing" status appears, sign the app. For instructions and more information, see About Signing. When re-signing an app that is already installed on any users' devices, you need to re-sign with the same signing credentials used to previously sign the app. If you do not, users will not be able to upgrade to the new version. With iOS, also remember to sign the app with signing credentials that were created using the same Apple account used to create the signing credentials for the App Catalog.

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

     

  6. Return to the Applications page and click the Edit link next to the app you just applied policies to. 
  7. Expand the Application section. 
  8. If you signed the app with Apperian, continue with the next step. If you signed the app using the signing package, upload the newly signed version.
  9. Select the Enabled check box. 
  10. In the Application Update Settings section, click Set to today. This marks the update as mandatory to ensure that all users who already have it installed will update to the latest version.
  11. Click OK
  • No labels