Povratne informacije Uredi

Tutorial: Configure Zscaler Beta for automatic user provisioning

  • Članak
  • 5 min. za čitanje

The objective of this tutorial is to demonstrate the steps to be performed in Zscaler Beta and Azure Active Directory (Azure AD) to configure Azure AD to automatically provision and de-provision users and/or groups to Zscaler Beta.

Note

This tutorial describes a connector built on top of the Azure AD User Provisioning Service. For important details on what this service does, how it works, and frequently asked questions, see Automate user provisioning and deprovisioning to SaaS applications with Azure Active Directory.

Prerequisites

The scenario outlined in this tutorial assumes that you already have the following:

  • An Azure AD tenant
  • A Zscaler Beta tenant
  • A user account in Zscaler Beta with Admin permissions

Note

The Azure AD provisioning integration relies on the Zscaler Beta SCIM API, which is available to Zscaler Beta developers for accounts with the Enterprise package.

Before configuring Zscaler Beta for automatic user provisioning with Azure AD, you need to add Zscaler Beta from the Azure AD application gallery to your list of managed SaaS applications.

To add Zscaler Beta from the Azure AD application gallery, perform the following steps:

  1. In the Azure portal, on the left navigation panel, click Azure Active Directory icon.

    The Azure Active Directory button

  2. Navigate to Enterprise Applications and then select the All Applications option.

    The Enterprise applications blade

  3. To add new application, click New application button on the top of dialog.

    The New application button

  4. In the search box, type Zscaler Beta, select Zscaler Beta from result panel then click Add button to add the application.

    Zscaler Beta in the results list

Assigning users to Zscaler Beta

Azure Active Directory uses a concept called "assignments" to determine which users should receive access to selected apps. In the context of automatic user provisioning, only the users and/or groups that have been "assigned" to an application in Azure AD are synchronized.

Before configuring and enabling automatic user provisioning, you should decide which users and/or groups in Azure AD need access to Zscaler Beta. Once decided, you can assign these users and/or groups to Zscaler Beta by following the instructions here:

Important tips for assigning users to Zscaler Beta

  • It is recommended that a single Azure AD user is assigned to Zscaler Beta to test the automatic user provisioning configuration. Additional users and/or groups may be assigned later.

  • When assigning a user to Zscaler Beta, you must select any valid application-specific role (if available) in the assignment dialog. Users with the Default Access role are excluded from provisioning.

Configuring automatic user provisioning to Zscaler Beta

This section guides you through the steps to configure the Azure AD provisioning service to create, update, and disable users and/or groups in Zscaler Beta based on user and/or group assignments in Azure AD.

Tip

You may also choose to enable SAML-based single sign-on for Zscaler Beta, following the instructions provided in the Zscaler Beta single sign-on tutorial. Single sign-on can be configured independently of automatic user provisioning, though these two features compliment each other.

Note

When users and groups are provisioned or de-provisioned we recommend to periodically restart provisioning to ensure that group memberships are properly updated. Doing a restart will force our service to re-evaluate all the groups and update the memberships.

To configure automatic user provisioning for Zscaler Beta in Azure AD:

  1. Sign in to the Azure portal and select Enterprise Applications, select All applications, then select Zscaler Beta.

    Enterprise applications blade

  2. In the applications list, select Zscaler Beta.

    The Zscaler Beta link in the Applications list

  3. Select the Provisioning tab.

    There is a list of tabs arranged into categories, and titled ZScaler Beta - Provisioning / Enterprise Application. The Provision tab of the Manage category is selected.

  4. Set the Provisioning Mode to Automatic.

    The Automatic mode has been selected from the Provisioning Mode drop-down list. There are fields for Admin Credentials, used to connect to the Zscaler Beta API, and there is a Test Connection button.

  5. Under the Admin Credentials section, input the Tenant URL and Secret Token of your Zscaler Beta account as described in Step 6.

  6. To obtain the Tenant URL and Secret Token, navigate to Administration > Authentication Settings in the Zscaler Beta portal user interface and click on SAML under Authentication Type.

    On Authentication Settings, in the Authentication Profile, the selected Directory Type is Hosted DB, and the selected Authentication Type is SAML.

    Click on Configure SAML to open the Configuration SAML options.

    On Configure SAML, the Enable SAML Auto-Provisioning and the Enable SCIM-Based Provisioning options are selected. The Base URL and Bearer Token text boxes are highlighted.

    Select Enable SCIM-Based Provisioning to retrieve Base URL and Bearer Token, then save the settings. Copy the Base URL to Tenant URL, and Bearer Token to Secret Token in the Azure portal.

  7. Upon populating the fields shown in Step 5, click Test Connection to ensure Azure AD can connect to Zscaler Beta. If the connection fails, ensure your Zscaler Beta account has Admin permissions and try again.

    On Admin Credentials, the Tenant URL and Secret Token fields have values, and the Test Connection button is highlighted.

  8. In the Notification Email field, enter the email address of a person or group who should receive the provisioning error notifications and check the checkbox Send an email notification when a failure occurs.

    The Notification Email text box is empty, and the Send an email notification when a failure occurs checkbox is cleared.

  9. Click Save.

  10. Under the Mappings section, select Synchronize Azure Active Directory Users to Zscaler Beta.

    The Synchronize Azure Active Directory Users to ZScalerBeta is selected and enabled.

  11. Review the user attributes that are synchronized from Azure AD to Zscaler Beta in the Attribute Mapping section. The attributes selected as Matching properties are used to match the user accounts in Zscaler Beta for update operations. Select the Save button to commit any changes.

    In the Attribute Mappings section for user attributes, the Active Directory attributes are shown next to the Zscalar Beta attributes they are synchronized with. One pair of attributes is shown as Matching.

  12. Under the Mappings section, select Synchronize Azure Active Directory Groups to Zscaler Beta.

    The Synchronize Azure Active Directory Groups to ZScalerBeta is selected and enabled.

  13. Review the group attributes that are synchronized from Azure AD to Zscaler Beta in the Attribute Mappings section. The attributes selected as Matching properties are used to match the groups in Zscaler Beta for update operations. Select the Save button to commit any changes.

    In the Attribute Mappings section for group attributes, the Active Directory attributes are shown next to the Zscalar Beta attributes they are synchronized with. One pair of attributes is shown as Matching.

  14. To configure scoping filters, refer to the following instructions provided in the Scoping filter tutorial.

  15. To enable the Azure AD provisioning service for Zscaler Beta, change the Provisioning Status to On in the Settings section.

    The Provisioning Status is shown and set to On.

  16. Define the users and/or groups that you would like to provision to Zscaler Beta by choosing the desired values in Scope in the Settings section.

    The Scope drop-down list is shown, and Sync only assigned users and groups is selected. The other available value is Sync all users and groups.

  17. When you are ready to provision, click Save.

    The Save button at the top of Zscaler Beta - Provisioning is highlighted. There is also a Discard button.

This operation starts the initial synchronization of all users and/or groups defined in Scope in the Settings section. The initial sync takes longer to perform than subsequent syncs, which occur approximately every 40 minutes as long as the Azure AD provisioning service is running. You can use the Synchronization Details section to monitor progress and follow links to provisioning activity report, which describes all actions performed by the Azure AD provisioning service on Zscaler Beta.

For more information on how to read the Azure AD provisioning logs, see Reporting on automatic user account provisioning.

Additional resources

Next steps