# SailPoint Juniper Mist Connector Documentation

> Juniper Mist Connector Documentation

# Documentation

# Connecting SailPoint and Juniper Mist

To connect SailPoint to the source, perform the following tasks:

## Adding and Configuring the Source in SailPoint

To connect to SailPoint, perform the following steps. Once the connection is made, you can configure it to meet your company's needs.

1. Go to **Admin \> Connections \> Sources**.
2. Select **Create New**.
3. Search for a source type and select **Actions**.
4. In the **Actions** dropdown, select the setup method:

   - **Express Setup** - Quickly create a read-only connection to your target system by providing minimal configurations and authentication. On completion, aggregation is automatically started.

     > **Note**
     >
     > Express Setup supports Credential Providers. For information on supported credential providers and configuration, refer to [Credential Providers](<https://documentation.sailpoint.com/connectors/help/credential_providers.html>). For more information, contact your SailPoint Customer Service Manager.
   - **Standard Setup** - Provide detailed basic configuration to create the source. Once the source is created, continue with source setup.

### Express Setup

1. Review the directions and select **Start Express Setup**.
2. Review the pre-populated source name, source owner, and description. To update, select **Edit**.

   > **Note**
   >
   > Source name must be unique.
3. (Optional) If enabled for your organization, select the **Use a Credential Provider** checkbox to manage the source's authentication using a credential provider.

   > **Note**
   >
   > To add a Credential Provider in SailPoint, go to **Admin \> Connections \> Credential Providers**. For more information about credential providers, refer to [Credential Providers](<https://documentation.sailpoint.com/connectors/help/credential_providers.html>).
4. Configure the authentication to allow SailPoint to connect to the source. For more information, refer to the **Connection Settings** page.
5. Select **Finish**. After a successful test connection, the system creates your source and prompts you to run an aggregation.

   - If you want to aggregate now, select **Aggregate**.

     - To see the latest account aggregation history, go to **Account Management \> Account Aggregation**.
     - To see the list of aggregated source accounts, go to **Account Management \> Accounts**.
   - If you want to aggregate later, select **Exit**. This returns you to the **Sources** page. Your new source is listed, but contains no accounts or aggregation history yet.

### Standard Setup

Configure more detailed settings relative to Express Setup.

1. In the **Source Name** field, enter a unique and descriptive name for your source. Source names cannot exceed 128 characters.
2. In the **Description** field, provide additional details about the source to help distinguish it from similar sources. This field allows a maximum of 2,000 characters.
3. In the **Source Owner** field, begin typing the name of an owner. Matches appear after you type two or more letters. For more information, refer to [Assigning a Source Owner](<https://documentation.sailpoint.com/saas/help/sources/index.html#assigning-a-source-owner>).
4. (Optional) Select a governance group to grant its members [source](<https://documentation.sailpoint.com/saas/help/common/users/user_levels.html#source-sub-admin-user-level>) or [role](<https://documentation.sailpoint.com/saas/help/common/users/user_levels.html#role-sub-admin-user-level>) sub-admin level oversight of the source and its access. For more information, refer to [Creating and Managing Governance Groups](<https://documentation.sailpoint.com/saas/help/common/users/governance_groups.html>).
5. If this source represents a primary system containing your organization's personnel records, select the **Authoritative Source** checkbox. For more information, refer to [Creating Identity Profiles](<https://documentation.sailpoint.com/saas/help/setup/identity_profiles.html>).
6. Select **Continue**. The source is created, and you are navigated to the **Source Setup \> Base Configuration** page. Here, continue to configure your connected source.

## Base Configuration

Provide the base configuration parameters. Information you entered in the Create New Source dialog is automatically entered into the fields in the Base Configuration page. You can edit this information if necessary.

1. Enter a descriptive **Source Name** for the connection.
2. Enter the **Source Description** that provides details necessary to distinguish it from similar connection sources.
3. In **Source Owner**, begin typing the name of the source owner.
4. (Optional) Select the appropriate **Governance Group for Source Management** from the dropdown list. For more information about governance groups, refer to [Associating Governance Groups with a Source](<https://documentation.sailpoint.com/saas/help/common/users/governance_groups.html#associating-a-governance-group-with-a-source>).
5. Select **Create Manual Work Items** to enable the source to support additional source management features such as creating accounts and access profile management.

   > **Important**
   >
   > Once you enable this feature, it can't be disabled.

   For more information on manual work items, refer to [Work Items](<https://developer.sailpoint.com/docs/api/work-items>). For more information on SailPoint features, refer to [SailPoint Identity Services](<https://documentation.sailpoint.com/saas/help/index.html>).
6. Select **Save**.

## Connection Settings

Configure a secured, direct connection to the source.

1. Enter the Juniper Mist API host for the organization's region as **Base URL**. For example, `https://api.gc4.mist.com`.
2. Enter the UUID of the Juniper Mist organization as **Organization ID**.
3. Enter the user or organization API token as **API Token**.
4. Select **Save**.

## Review and Test

Perform a test to confirm the connection to SailPoint.

1. Go to **Review and Test**.
2. Confirm that the entries in each field are correct.

   If you note any mistakes, return to the section and make corrections.
3. Select **Test Connection**.

## SailPoint Application Onboarding

SailPoint application onboarding enables you to easily onboard new applications and create sources following the successful onboarding of a discovery source. To use this feature, continue to **Discovered Applications** in the SailPoint user interface.

For more information, refer to [Application Onboarding](<https://documentation.sailpoint.com/saas/help/ai/app_onboarding/index.html>) in the SailPoint SaaS documentation.

# Integrating SailPoint with Juniper Mist

Juniper Mist is a cloud-managed networking platform for Wi-Fi, wired, and WAN. Organisations manage their network from the Juniper Mist portal. The people who sign in to that portal are administrators. This document covers how to configure a new direct connection between SailPoint and Juniper Mist for Quick Compliance. For a reference to the terminology specific to SailPoint products, refer to [Source and Connector Definitions](<https://documentation.sailpoint.com/saas/help/sources/index.html#source-and-connector-definitions>).

> [!NOTE]
>
> To view the latest features, enhancements, and fixes for all SaaS connectors, refer to the [SaaS Release Notes](<https://community.sailpoint.com/release-notes/saas>) page.

## Supported Features

The Juniper Mist connector supports the following:

### Account Management

- Aggregate Account (Administrators)

### Entitlement Management

- Aggregate Sites
- Aggregate Site groups

> [!NOTE]
>
> This connector is read-only. It supports test connection, account aggregation, and entitlement aggregation for Quick Compliance. Provisioning, de-provisioning, and write operations are not supported.

> [!IMPORTANT]
>
> Quick Compliance connectors have the following manual aggregation limits within a 24-hour period:
>
> - **Organization Admins**: Limited to 3 manual account or entitlement aggregations per day per source. This limit is cumulative across all admins in the organization.
> - **Regular Users**: Limited to 1 manual account or entitlement aggregation per day per source.
>
> These limits ensure that individual compliance statuses are kept up to date while maintaining continuous compliance monitoring. If you need to run additional aggregations beyond these limits, contact SailPoint Support.

## Prerequisites

Complete these steps in Juniper Mist before you add the source in SailPoint.

### Identify Your Region and Base URL

Juniper Mist organisations live in a specific cloud region. The API host must match that region, or authentication fails with an invalid token. Sign in to the Juniper Mist portal and look at the address bar. Replace `manage` with `api`, and use `https://`. For example, you sign in at `https://manage.gc4.mist.com/admin/?org_id=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx`

- **Base URL**
- **Organisation ID**: the UUID after `org_id=`

| Region | Portal | Base URL |
| --- | --- | --- |
| Global 01 | [manage.mist.com](<https://manage.mist.com>) | `https://api.mist.com` |
| Global 02 | [manage.gc1.mist.com](<https://manage.gc1.mist.com>) | `https://api.gc1.mist.com` |
| Global 03 | [manage.ac2.mist.com](<https://manage.ac2.mist.com>) | `https://api.ac2.mist.com` |
| Global 04 | [manage.gc2.mist.com](<https://manage.gc2.mist.com>) | `https://api.gc2.mist.com` |
| Global 05 | [manage.gc4.mist.com](<https://manage.gc4.mist.com>) | `https://api.gc4.mist.com` |
| EMEA 01 | [manage.eu.mist.com](<https://manage.eu.mist.com>) | `https://api.eu.mist.com` |
| EMEA 02 | [manage.gc3.mist.com](<https://manage.gc3.mist.com>) | `https://api.gc3.mist.com` |
| EMEA 03 | [manage.ac6.mist.com](<https://manage.ac6.mist.com>) | `https://api.ac6.mist.com` |
| EMEA 04 | [manage.gc6.mist.com](<https://manage.gc6.mist.com>) | `https://api.gc6.mist.com` |
| APAC 01 | [manage.ac5.mist.com](<https://manage.ac5.mist.com>) | `https://api.ac5.mist.com` |
| APAC 02 | [manage.gc5.mist.com](<https://manage.gc5.mist.com>) | `https://api.gc5.mist.com` |
| APAC 03 | [manage.gc7.mist.com](<https://manage.gc7.mist.com>) | `https://api.gc7.mist.com` |

### Create an API Token

Juniper Mist authenticates with a static API token. There is no OAuth login from SailPoint.

1. Sign in to the portal for your organisation's region.
2. Create a token. Prefer an organisation API token (**Organisation \> Admin \> Settings \> API Token**) so aggregation is not tied to one person's account. You can also create a user API token from your account menu.
3. Copy the token immediately. Juniper Mist shows the full value only at creation.

The token is sent on every request as `Authorization: Token <API Token>`.

### Record These Values for SailPoint

- **Base URL** (regional API host, including `https://`)
- **Organisation ID** (UUID)
- **API Token**

## Required Permissions

A Juniper Mist administrator who can create an organisation or user API token for the organisation you want to aggregate must create the token. SailPoint sends the API token on each request. There is no token refresh. If the token is revoked, expired, or created in a different region than the Base URL, test connection and aggregation fail until a valid token for that region is supplied. Juniper Mist allows 5000 API calls per hour per token. For more information about Juniper Mist, refer to the following:

- [Juniper Mist website](<https://www.mist.com/>)
- [Mist API introduction](<https://www.mist.com/documentation/mist-api-introduction/>)
- [API Endpoints and Global Regions](<https://www.juniper.net/documentation/us/en/software/mist/automation-integration/topics/topic-map/api-endpoint-url-global-regions.html>)
- [RESTful API Overview](<https://www.juniper.net/documentation/us/en/software/mist/automation-integration/topics/concept/restful-api-overview.html>)

> [!NOTE]
>
> The linked document is not maintained by SailPoint and is subject to change without notice.

# Schema Reference

The application schema is used to configure the objects returned from a connector.

> [!NOTE]
>
> - The **Account Schema** tab is used to define the attributes for each object type in the application being configured. The schema attributes can be defined as **Entitlement** or **Multi-Valued**. Refer to [Managing Source Account Schemas](<https://documentation.sailpoint.com/saas/help/accounts/schema.html>) for more information.
> - The schema attributes that are not present by [default](<#default-account-schema>) must be defined as strings if not specified.

The Juniper Mist connector uses the following default correlation and object configurations.

## Default Account Schema

Each source supports a variety of details, or attributes, about each user who has an account, such as their name, email address, manager name, and location.

The set of account attributes each source stores and how they're organized is known as the account's *schema*. To best represent your data, you can configure sources to use an account schema matching the one you use in the external connector. Refer to [Managing Source Account Schemas](<https://documentation.sailpoint.com/saas/help/accounts/schema.html>) for more information.

### Default Account ID

SailPoint requires that certain attributes remain in your configuration. These attributes are referred to as *account IDs*.

> [!CAUTION]
>
> Changing the attribute marked as the account ID after aggregating accounts can result in duplicate accounts being created. To avoid this, either reset the accounts on this source before editing the account ID attribute or edit the account ID attribute before aggregating accounts.
>
> To resolve issues caused by changing account IDs, reconfigure them to their default values.

The following table lists the default account IDs for this connector:

| Account ID | Schema Object Type |
| --- | --- |
| adminId | Administrator |

### Default Account Attributes

The Juniper Mist connector supports the following default account schema attributes and customer configurable attributes. The attributes must be defined as strings if not specified.

| Attribute Name | Description |
| --- | --- |
| adminId | Unique identifier of the administrator |
| email | Email address used to sign in to the portal |
| firstName | First name of the administrator |
| lastName | Last name of the administrator |
| name | Display name returned, when present |
| viaSso | Indicates whether the administrator signs in through SSO |
| twoFactorVerified | Indicates whether the administrator has verified two-factor authentication |
| twoFactorEnabled | Indicates whether two-factor authentication is enabled |
| tags | Tags assigned to the administrator |
| passwordModifiedTime | Epoch time when the administrator password was last modified |
| lastLogin | Epoch time of the administrator's last login, when returned |
| created | Epoch time when the administrator was created, when returned |
| role | Roles assigned across the administrator's privileges |
| privilegeScopes | Scopes represented in the administrator's privileges |
| privilegeNames | Privilege names returned |
| views | Portal views assigned through administrator privileges |
| sites | Sites directly assigned to the administrator |
| siteGroups | Site groups assigned to the administrator |

## Default Entitlement Attributes

Entitlement attributes define the entitlements, such as groups or roles, that can be assigned to the managed system's user accounts. Refer to [Managing Entitlements](<https://documentation.sailpoint.com/saas/help/access/entitlements.html>) for more information.

> [!CAUTION]
>
> Changing the attribute marked as the Entitlement ID after aggregating accounts or entitlements can result in duplicate entitlements being created, or access profiles and roles breaking. To avoid this, edit the entitlement schema before performing any aggregations.

### Default Site Attributes

| Attribute Name | Description |
| --- | --- |
| id | Unique identifier of the site |
| name | Name of the site |
| address | Street address of the site |
| timezone | Time zone configured on the site |
| countryCode | Country code of the site |
| siteGroupIds | Site groups that associated with the site |
| createdTime | Epoch time when the site was created |
| modifiedTime | Epoch time when the site was last modified |

### Default SiteGroup Attributes

| Attribute Name | Description |
| --- | --- |
| id | Unique identifier of the site group |
| name | Name of the site group |
| siteIds | Sites that belong to the site group |
| createdTime | Epoch time when the site group was created |
| modifiedTime | Epoch time when the site group was last modified |