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

Administrators can manage stored signing credentials for iOS and Android apps on the Settings page in the Admin Portal. This saves time during the signing process by allowing you to select appropriate credentials from a list. It also removes the need for multiple administrators to obtain and store all necessary credentials on their local machines.

Storing signing credentials is a convenient option, but you are not required to store any signing credentials in order to sign with the Admin Portal. Administrators can also sign with new credentials during the signing process. When you provide new credentials during signing, you can use them that one time only, or you can can choose to save the credentials for future use. Saving the credentials has the same result as the procedure on this page.

For more information about signing, see Signing.

Before you Begin

Ensure that you have all required files and passwords. For details, see Signing Prerequisites.

iOS App Extensions

If you are adding signing credentials for an iOS app that has a app extensions, be sure to collect all the distribution provisioning profiles needed to sign the app and all its extensions. To simplify this process, you may want to add the signing credentials from the Signing tab for the app. On the Signing tab of an app, there is a section to Sign with New Credentials; this section lists a line for the app and each of its extensions. It functions as a checklist, to help you verify that you have uploaded all the provisioning profiles that you need. After you have uploaded the certificate and provisioning profiles, you can select to save the credentials for future use.

Back to Top

Add Credentials

You can save credentials in the Apperian database to save time during the signing process.

To add new credentials
  1. On the ADmin Portal navigation bar, click Settings.
  2. Click the Signing Credentials tab.
  3. Click Add New Credentials to display fields for defining the credentials. All fields are required except Password.
  4. In the Description field, enter a description for the credentials. This description should help you or another Apperian administrator choose the most suitable credentials from a list of credentials during the signing process. For example, if you are uploading credentials for signing a specific app, then the name should include the app name. During signing, Apperian will list credentials for the correct platform only, so you do not need to specify "iOS" or "Android" in the description. Note that you can modify this field at any time after saving the credentials.

  5. From the Platform list, select Android or iOS to choose the type of app that you can sign with the credentials.
  6. In the Key/Certificate P12 File field, browse to select the certificate file in PKCS (Personal Information Exchange File) #12 format. The file must have a .p12 extension. 
  7. (Optional) In the Password field, enter the password for the certificate file:

    • For iOS certificates, this is a password that was defined for the distribution certificate when it was exported from the Login Keychain to a .p12 file.
    • For Android certificates, this is a password that was created when the Java Keystore was imported to a .p12 file.

    If the certificate file was created with a password, and you do not store that password with the credentials, you are prompted for the password when you sign an app.

     

  8. (iOS only) In the Provisioning Profile field, browse to select a distribution provisioning profile file that is associated with the certificate you uploaded. The file must have a .mobileprovision extension. 

    If you are adding credentials to sign an app that contains extensions, you will most likely need to upload multiple distribution provisioning profiles. For more information, see App Extensions and Entitlements.

    To upload additional provisioning profiles:

    1. Click the + Add Profile button to display another Provisioning Profile field. Browse to select another .mobileprovision file. 
    2. Continue adding profiles until you have added all the profiles needed to sign the app you plan to sign with the set of credentials.
  9. By default, the Validate credentials checkbox is selected. This tells Apperian to validate the credentials when you click Save. Validation looks for issues such as an incorrect password or corrupt certificate file.

    If you do not want to validate the credentials before saving them, clear the Validate credentials check box. Apperian saves the credentials even if they are not valid; you won't receive an error until you attempt to sign an app with the invalid credentials.

    Note that if your certificate has a password assigned to it but you did not provide a password in step 7, you should clear the Validate credentials check box; Apperian can't validate the credentials without the password.

  10. Click Save to save the credentials. If you chose to validate credentials, Apperian informs you of any issues it encounters.

When credentials are saved successfully, an entry is added to the list of credentials. You can modify the description field at any time. To change anything else, you must delete the credentials and add new credentials. If you upload multiple distribution provisioning profiles together, they are all listed in the Provisioning Profile column. 

Back to Top

Delete Credentials

You can delete signing credentials that you no longer want to store in the Apperian database. Deleting credentials from the database has no impact on apps that were already signed with those credentials.

To delete credentials
  1. On the Admin Portal navigation bar, click Settings.
  2. Click the Signing Credentials tab.
  3. Select the check box for the credentials you want to delete. To select all credentials, click the Select All link.
  4. Click Delete and then click Delete again in the confirmation message box.

Back to Top


 

  • No labels