The cloud application catalog is populated with Web applications. These applications include some information in their application records. When you add a Web application to your catalog from the cloud application catalog, you must provide additional information to complete the application record. You might also need to work with your Web application account representatives to complete other required setup.

Many of the applications in the cloud application catalog use Security Assertion Markup Language (SAML 1 or SAML 2) to exchange authentication and authorization data to verify that users can access a Web application.

When you add a Web application to the catalog, you are creating an entry that points indirectly to the Web application. The entry is defined by the application record, which is a form that includes a URL to the Web application.

You can apply an access policy to control user access to the application. If you do not want to use the default access policy, create a new one. See Workspace ONE Access Administration Guide for information about managing access policies.

Procedure

  1. In the administration console, click the Catalog tab.
  2. Click Add Application > Web Application ...from the cloud application catalog.
  3. Click the icon of the Web application you want to add.
    The application record is added to your catalog, and the Details page appears with the name and authentication profile already specified.
  4. (Optional) Customize the information on the Details page for your organization's needs.
    Items on the page are populated with information specific to the Web application.
    You can edit some of the items, depending on the application.
    Form Item Description
    Name The name of the application.
    Description A description of the application that users can read.
    Require VMware Browser Enable this check box to require this application to only open in the VMware Browser when the app is access through the Workspace ONE app on iOS and Android devices.
    Icon

    Click Browse to upload an icon for the application. Icons in PNG, JPG, and ICON file formats, up to 4MB, are supported.

    Uploaded icons are resized to 80px X 80px.

    To prevent distortion, upload icons where the height and width are equal to each other and as close as possible to the 80px X 80px resize dimensions.

    Categories To allow the application to appear in a category search of catalog resources, select a category from the drop-down menu. You must have created the category earlier.
  5. Click Save.
  6. Click Configuration, edit the application record's configuration details, and click Save.

    Some of the items on the form are prepopulated with information specific to the Web application. Some of the prepopulated items are editable, while others are not. The information requested varies from application to application.

    For some applications, the form has an Application Parameters section. If the section exists for an application and a parameter in the section does not have a default value, provide a value to allow the application to launch. If a default value is provided, you can edit the value.

  7. Select the Entitlements, Licensing, and Provisioning tabs and customize the information as appropriate.
    Tab Description
    Entitlements Entitle users and groups to the application. You can configure entitlements while initially configuring the application or anytime in the future.
    Access Policies

    Apply an access policy to control user access to the application.

    Licensing Configure license tracking. Add license information for the application to track license use in reports.
    Provisioning

    Select a provisioning adapter, if applicable.

    Provisioning provides automatic application user management from a single location. Provisioning adapters allow the Web application to retrieve specific information from the Workspace ONE Access service as required. For example, to enable automatic user provisioning to Google Apps, user account information, such as the user name, first name, and last name must exist in the Google Apps database. An application might require other information, such as group-membership and authorization-role information.

    See Using Provisioning Adapters for more information.

What to do next

For details about adding user and group entitlements for Web applications, see Assigning Users and Groups to a Web Application.