# SailPoint Sumo Logic SaaS Connector Documentation > Sumo Logic SaaS Connector Documentation # Documentation # Connecting SailPoint and Sumo Logic SaaS To connect SailPoint with Sumo Logic, perform the following tasks: ## Adding 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. > [!IMPORTANT] > > By default, the provisioning feature is **disabled**, and the connector only supports read-only operations. To support provisioning operations, you must manually enable the feature in the source configuration. **To configure a new source:** 1. Sign in to SailPoint. 2. Go to **Admin \> Connections \> Sources**. 3. Select **Create New**. 4. Search for the connector by entering the name in the search box, and then select **Configure**. 5. In the **Source Name** field, enter a unique and descriptive name for your source. Source names cannot exceed 128 characters. 6. 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. 7. 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](). 8. (Optional) Select a governance group to grant its members [source]() or [role]() sub-admin level oversight of the source and its access. For more information, refer to [Creating and Managing Governance Groups](). 9. 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](). 10. Select **Continue**. The source is created, and you are navigated to the **Source Setup \> Base Configuration** page. Continue to configure your connected source there. ## 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 unique name and description for the source. 2. In the **Source Owner** dropdown list, select the identity that owns this source. - To find a source owner, begin entering their name. 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, go to **Admin \> Connections \> Credential Providers**. For more information about credential providers, refer to [Credential Providers](). 4. Configure the authentication to allow SailPoint to connect to the source. Refer to [Connection Settings](<#connection-settings>) for more information. 5. (Optional) In the **Governance Group for Source Management** dropdown list, select a governance group to associate with this source. For more information about governance groups, refer to [Associating Governance Groups with a Source](). 6. (Optional) Choose whether to enable or disable provisioning for the source. Provisioning is disabled by default. - **Enable Provisioning** - Set the toggle to **Enabled** to allow the source to create, update, and deactivate accounts in the connected source system. - **Disable Provisioning** - Set the toggle to **Disabled** to disable provisioning for the source. Disabling provisioning will prevent the creation, updating, or deactivating of accounts on this source. 7. Select **Save**. ## Connection Settings The following information is required for SailPoint to connect and interact with Sumo Logic. > [!NOTE] > > **Screenshot** > > [![Connection Settings]()]() 1. Select **Connection Settings** from the menu on the left of the screen. 2. Enter the API URL from the [Prerequisites]() section into the **API URL** field. 3. Enter the Access ID into the **Access ID** field. 4. Enter the Access Key into the **Access Key** field. 5. 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]() in the SailPoint SaaS documentation. # Integrating SailPoint with Sumo Logic SaaS Sumo Logic, Inc. is a cloud-based machine data analytics company focusing on security, operations and BI use cases. It provides log management and analytics services that leverage machine-generated big data to deliver real-time IT insights. This document is designed to give specific information about the requirements and fields needed to successfully configure an instance of the Sumo Logic source. > [!NOTE] > > To view the latest features, enhancements, and fixes for all SaaS connectors, refer to the [SaaS Release Notes]() page. ## Supported Features The Sumo Logic source supports the following features: - Access Certifications (Certifications of entitlements connected to the accounts) - Aggregation of Accounts - Aggregation of Entitlements (Roles) - Get Account - Provisioning - Create Account - Add/Remove Entitlement (Roles) > **Note** > > Due to SumoLogic API limitations, at least one role must always be present for the user account. If you try to remove/revoke all the access/roles at once, the API might throw an error, such as `last role cannot be removed`. - Update Account - Delete Account - Enable/Disable Account - Unlock Account ## Prerequisites The user must create an **Access ID** and **Access Key** in Sumo Logic to support all of the features. An **API URL** is needed for connecting to the Sumo Logic server. > [!NOTE] > > API Endpoint is region based. Reference the table below and use the URL for your region. | Deployment | API Endpoint | | --- | --- | | AU | `https://api.au.sumologic.com` | | CA | `https://api.ca.sumologic.com` | | DE | `https://api.de.sumologic.com` | | EU | `https://api.eu.sumologic.com` | | FED | `https://api.fed.sumologic.com` | | IN | `https://api.in.sumologic.com` | | JP | `https://api.jp.sumologic.com` | | US1 | `https://api.sumologic.com` | | US2 | `https://api.us2.sumologic.com` | ## Service Account Permission The user with Administrator role or a role that has "Manage users and roles" capability, must create an Access ID and Access Key in Sumo Logic to support all of the features. # Machine Account Attributes ## Machine Account Provisioning Attributes The following table lists the attributes in the machine account creation template, including the generator and description for each attribute. | Attribute | Generator | Description | | --- | --- | --- | | email | Static | Email of the account | | firstName | Static | First name of the account | | lastName | Static | Last name of the account | For more information, refer to [Machine Identity Security Overview](). # Provisioning The Sumo Logic SaaS connector supports provisioning, allowing you to create and manage accounts and entitlements in Sumo Logic directly from SailPoint. **Prerequisite:** Your system is configured for provisioning. When SailPoint provisions new accounts to the source, it uses the attributes on the **Create Account** page as instructions or a template for what to include in the account. This page is also referred to as the *provisioning policy*. When new access is granted on a source where a user does not already have an account, SailPoint automatically includes account creation in the provisioning. This applies whether provisioning is started from an access request or from an automated role or lifecycle state assignment. For direct-connect sources, SailPoint automatically creates the account from this configuration. If the source is not configured as a direct-connect source, SailPoint creates and assigns a provisioning task to the source owner and includes the values for the source owner to use in manually creating the account. > [!IMPORTANT] > > This section describes the default **Create Account** configuration. SailPoint recommends that you work with Services to define a provisioning configuration specific to your company's needs. Be sure to verify large changes to the provisioning policy before implementation. Failure to do so might cause provisioning to fail. ## Default Create Account Attributes | Attribute Name | Display name | Required | Type | Attribute Mapping | Description | | --- | --- | --- | --- | --- | --- | | email | Email | True | String | Work Email (email) | Identity Attribute: The email address of the member account as taken from the Work email of Identity. | | firstName | First Name | True | String | firstname | Identity Attribute: The firstName of the member account as taken from the firstname of Identity. | | lastName | Last Name | True | String | lastname | The lastName of the member account as taken from the lastname of Identity. | > [!NOTE] > > Multiple entitlements can be assigned to the user via Access Profiles. Multiple Access profiles requested at the same time are not supported. # 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]() for more information. > - The schema attributes that are not present by [default](<#default-account-schema>) must be defined as strings if not specified. The Sumo Logic SaaS connector uses the following default correlation and object configurations. ## Default Correlation Configuration Before you aggregate accounts from this source, you can map account attributes with their corresponding identity attributes based on your requirements. You can customize the correlation configuration. Refer to [Assigning Source Accounts to Identities]() for more information. When you first create the Sumo Logic SaaS source, the default correlation mapping is: | Account Attribute | Operation | Identity Attribute | | --- | --- | --- | | email | Equals | Work Email (email) | | firstName | Equals | Given Name (firstname) | | lastName | Equals | Family Name (lastname) | ## 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]() for more information. ### Default Account Attributes The Sumo Logic SaaS 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 | | --- | --- | | id | The user's unique ID | | firstName | The user's first name | | lastName | The user's last name | | email | The user's email address | | roleIds | Roles assigned to the user | | createdAt | The user's creation timestamp in UTC format | | createdBy | ID for user who created this user | | modifiedAt | Last modification timestamp in UTC format | | modifiedBy | ID for user who modified this user | | isActive | The user's active status | | isLocked | The user's lock status | | isMfaEnabled | Multifactor authentication enablement status | | lastLoginTimestamp | Timestamp of the user's last login in UTC format | ## 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]() 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. | Attribute Name | Description | | --- | --- | | id | The role's unique ID | | name | The role's name | | description | The role's description | | users | Users assigned to this role | | capabilities | The role's capabilities | | autofillDependencies | The role's autofill dependencies | | createdAt | The role's creation date | | createdBy | Role Created By | | modifiedAt | Role Modified By | | modifiedBy | Role Modified Date | | systemDefined | Role is system or user defined | # Troubleshooting If you encounter any of the following issues or errors, SailPoint recommends that you follow the guidance provided below to resolve the error before contacting SailPoint Support. For issues or errors that are not addressed in this connector guide, refer to the following resources for troubleshooting information: - [SailPoint Identity Services Documentation]() - [SailPoint Support Knowledge Base]() - [SailPoint Developer Community]() ## Debug Logs For information about managing additional source settings, including debug logging and downloading connector logs, refer to [Managing Additional Settings]().