# SailPoint SAP Fieldglass SaaS Connector Documentation > SAP Fieldglass SaaS Connector Documentation # Documentation # Connecting SailPoint and SAP Fieldglass SaaS To connect SailPoint with SAP Fieldglass, 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 **Actions**. 5. In the **Actions** dropdown list, select the setup method: - [**Express Setup**](<#configuring-a-source-using-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](). For more information, contact your SailPoint Customer Service Manager. - [**Standard Setup**](<#configuring-a-source-using-standard-setup>) - Provide detailed basic configuration to create the source. Once the source is created, continue with source setup. ### Configuring a Source Using Express Setup Express Setup minimizes the initial configuration process so you can quickly connect the application and immediately begin aggregating user account and entitlement data. 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** > > The source name must be unique. You can change these settings later in the source configuration. 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](). 4. Configure the authentication to allow SailPoint to connect to the source. For more information, refer to the **Connection Settings** section. 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. ### Configuring a Source Using Standard Setup Use Standard Setup to configure the connector for full feature support. 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](). 4. (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](). 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](). 6. 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 > [!NOTE] > > **Screenshot** > > [![Connection Settings]()]() 1. Select **Connection Settings** from the menu. 2. Enter the SAP Fieldglass base URL in **Host URL**. 3. Enter the **Username** and **Password** of the SAP Fieldglass account. 4. Enter the **Application Key** from the SAP Fieldglass application. 5. Select **Save**. ## Aggregation Settings > [!NOTE] > > **Screenshot** > > [![Aggregation Settings]()]() [![Aggregation Settings]()]() [![Aggregation Settings]()]() 1. Select **Aggregation Settings** from the menu. 2. Enter the **User Report ID**, the **Worker Report ID**, and the **Single Worker Report ID**. 3. Enable **Aggregate Future Workers** to include users with future hire dates in account aggregation. 4. In **Future Workers Offset**, enter the number of days ahead (in the future) of the current date to aggregate future worker accounts. 5. Enable **Aggregate Terminated Workers** to include terminated workers in account aggregation. 6. In **Terminate Workers Offset**, enter the number of days prior to the current date to aggregate terminated worker accounts. 7. Enter a **PageSize** as the number of records that you can fetch in one request. The default page size is 50. The maximum value is 350. 8. Select **Save**. ## Provisioning Settings > [!NOTE] > > **Screenshot** > > [![Provisioning Settings]()]() 1. Select **Provisioning Settings** from the menu. 2. Enter the **Connector Integration Variant** name. 3. 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 SAP Fieldglass SaaS > [!NOTE] > > **Integration** > > This is an integration and requires additional licensing or subscriptions to utilize it. For more information, contact your customer success manager. SAP Fieldglass is a Vendor Management System (VMS) that helps manage a contingent workforce and buyer company users. It helps businesses manage flexible workforces better, faster, and with more efficient control. It increases productivity by streamlining processes such as assignment management, contingent workforce management, services procurement, and worker profile management. The SAP Fieldglass SaaS cloud integration with SailPoint's connector provides Identity Governance on buyer company users such as hiring managers, permanent employees of the buyer company, program management office users, and workers provided by Fieldglass. The integration also supports enforcing policies and permissions for granting and revoking access to buyer identities. > [!NOTE] > > To view the latest features, enhancements, and fixes for all SaaS connectors, refer to the [SaaS Release Notes]() page. ## Supported Features The SAP Fieldglass SaaS connector supports the following features: > [!IMPORTANT] > > Before you can use any of the following items marked with an asterisk (\*), SailPoint must activate the feature for your site. - Aggregation - Account Aggregation - Groups Aggregation - Add/Remove Entitlement - Groups - Account Provisioning - Create User - Update User (Attributes) - Enable/Disable User For more information on features, refer to [Source Features](). ## Privilege Classification SailPoint Privilege Classification helps organizations systematically categorize and manage the privilege levels of entitlements within their sources. By classifying entitlements as high, medium, or low, administrators can better understand the potential risk and impact associated with specific access rights. This allows automatic assignment of privilege levels based on system recommendations, custom-defined criteria, or a same level across all entitlements. | Privilege Level | Description | | --- | --- | | High | Administrative level access to accounts | | Medium | Administrative level access for a specific role or function | | Low | Only basic access of data | > [!NOTE] > > To manage Privilege Classification, users must have administrative roles such as Org Admin, Source Admin or Source Sub-Admin. For more information, refer to [Managing Privilege Classification](). > [!NOTE] > > **Example** > > [![Recommended Privilege Level - High]()]() > > [![Recommended Privilege Level - Medium]()]() ## Prerequisites You must set up a Client Application to establish SAP Fieldglass integration with SailPoint and perform all the operations. The client application uses the OAuth 2.0 client credentials to request a new access token as the initial step of accessing protected resources of SAP Fieldglass services. ### Create the X-Application Key > [!NOTE] > > **Screenshot** > > [![Create the X-Application Key]()]() [![Create the X-Application Key]()]() 1. Sign in to Fieldglass with **Buyer** credentials. 2. Go to the linked accounts of the signed-in user as **Configuration Manager**. 3. Select the **API Application Key** tile. 4. Select **New**. 5. Enter your **Application Name** and **Description**. 6. Select **Create**. You will now see the details as **UserName** (Client ID), **Password** (Client Secret), **Application Key**, and **Application Name**. 7. Select **New** to create a new Web service for the created **Application Key**. 8. Set the Status as **Enabled**. 9. Select **Save**. ### Create the Report > [!IMPORTANT] > > You will need *Analytics* access for creating and updating the Fieldglass reports. > [!NOTE] > > The report creation steps are the same for all Fieldglass modules. In our case we need Buyer and Worker modules for report creation. 1. Create a report folder named *SailPoint* to maintain reports needed for the Fieldglass source. In SAP Fieldglass, go to **Admin Configuration \> Reports \> Report Folder** and create the *SailPoint* folder. Folders created under the SailPoint folder are used to associate reports to user roles. > **Screenshot** > > [![Create report folder]()]() 2. From the home page, select the **Analytics** button, and then select **Create Report**. 3. Select the desired reporting category. For example: User, Worker, etc. A report template based on your selection will appear. You will need to create three reports: - User Report - Worker Report - Single Worker Report #### User Report Settings 1. For **User Report Settings**, select **Edit Report \> ASC** > **Screenshot** > > [![User Report Settings]()]() 2. Set the report filters as shown in the following screenshot. > **Screenshot** > > [![Report filters]()]() 3. Select **Details**, and then select the **JSON** radio button. > **Screenshot** > > [![Report details]()]() 4. Select the **Visibility** settings. > **Screenshot** > > [![Report visibility]()]() #### Single Worker Report Settings > [!NOTE] > > The following fields, filters, and details are required for each report creation of the Worker Report and Single Worker Report. This information is needed for worker data aggregation. 1. For **Worker Report Settings**, select **Edit Report \> ASC**. > **Screenshot** > > [![Worker report settings]()]() [![Worker report settings]()]() 2. The **SP Consolidated Worker ID** is a custom field. It must be created using the **Add Formula** link on the report creation page with the following details. > **Screenshot** > > [![Worker ID formula]()]() [![Worker ID formula]()]() #### Worker Report Settings 1. For **Worker Report Settings**, select **Edit Report \> ASC**. > **Screenshot** > > [![Worker report settings]()]() [![Worker report settings]()]() 2. Create two more fields. - **SP Worker Start date**. Formula: ```text [Worker | Details | Worker Start Date] ``` > **Screenshot** > > [![Worker start date]()]() - **SP Worker End Date** Formula: ```text ISBLANK([Worker | Details | Worker End Date],"12/31/9999") ``` > **Screenshot** > > [![Worker end date]()]() 3. Select **Validate** to validate the formula. 4. The following filters are mandatory to fetch the workers' report. However, users can change the values of the filters according to their requirements. The date format in User Preferences must be set to MM/DD/YYYY. > **Screenshot** > > [![Worker report filters]()]() 5. Select **Details**, and then select the **JSON** radio button. > **Screenshot** > > [![Worker report details]()]() 6. Select the **Visibility** settings. > **Screenshot** > > [![Report visibility]()]() 7. Templates can be modified based on the requestors' needs. From the **Fields** side bar, any field can be added to the current template via the drag and drop method. The columns can be reordered and renamed, and the values can be sorted in ascending or descending order. Filters can be applied regarding time or a specific status on the report. > **Note** > > - Remember that the template filters differ based on the reporting category selected earlier. > - **SP Worker End Date** and **SP Worker Start Date** will be overridden with the current date when aggregation executes. Additionally, if the **Future** or **Terminated offset** is configured. then it is used along with the current date to fetch the worker records. 8. Once the report has been configured, give it a name and choose the desired output format. 9. Select the **Show More Configuration** link, and set the **API Enabled** option to **Yes**. 10. **Save** the report. #### How to obtain the ID of the Report You will need the ID of the created report to provide in **Aggregation Settings** for the user and worker configurations. 1. Select your report name from the list. 2. Select the **Edit** option 3. The link url will contain the ID of the report > **Screenshot** > > [![Report ID]()]() ### Create the Connector Integration 1. Sign in with Configuration Manager access to the SAP Fieldglass portal. 2. Go to **Connectors** integration tools. 3. Search and open the **User Upload** connector from the connector list. 4. Select **Actions** and then select the **Create Variant** option to set the connector integration variant for provisioning. 5. Select **Start**, and then go to the **Enable** step. Enter the new connector name and select the values as shown below, then select **Next**. > **Screenshot** > > [![Create connector integration - enable]()]() 6. Enter the **Setup** details as shown below. > **Screenshot** > > [![Create connector integration - setup]()]() 7. Keep the default value as-is on the **Header Values** window. 8. In the **Security** window, change the value for the **Sensitive Data** and **Enable connector to be used through user interface? (optional)** fields. > **Screenshot** > > [![Create connector integration - security]()]() 9. Keep the default settings as-is in the **Configure Column Transformation** window and the **Connectivity** window. > **Screenshot** > > [![Create connector integration - connectivity]()]() 10. Select **Next** to finish. 11. Use the variant name created in the **Connector Integration Variant** field for the source. ### Configure Additional Attributes via Report This configuration is needed when you want to GET or SET the attributes other than those included out-of-the-box. #### SAP Fieldglass Configuration 1. In SAP Fieldglass, go to the existing **User Report** and select **Edit**. 2. Go to **Fields \> Name** and enter the name you want to search for. 3. Select the magnifying glass to perform the search. > **Screenshot** > > [![Configure additional attributes via report]()]() 4. Drag and drop fields from the navigation pane into the Columns area to add it (as a column) to your report. 5. Select **Save**. #### Connector Configuration 1. Add the new schema attribute by going to the **Source \> Schema Attribute \> New Schema Attribute**. 2. Add the attribute you need and then select **Save**. 3. Add the json mapping for the attribute under the \ via rest api to the source. For example, ```text example entry for currency field ``` ### Configure Additional Attributes with SCIM SailPoint supports SCIM for some additional attributes. You can configure them by performing the following steps: 1. Add the new schema attribute by going to **Source \> Schemas \> Add New Schema Attribute**. The attribute must have a complex name. For example, addresses.work.primary.locality 2. Add the json path for the attribute under the key "jsonPathMapping" For example, `` ## Required Permissions The SAP Fieldglass Service user must have the following two roles assigned to perform connector operations: - Configuration Manager - Administrator # Machine Account Attributes ## Machine Account Provisioning Attributes Machine account creation uses the same source attributes as standard account creation. For the complete list of supported attributes and their descriptions, refer to [Provisioning Policy Attributes](). For more information, refer to [Machine Identity Security Overview](). # Provisioning The SAP Fieldglass SaaS connector supports provisioning, allowing you to create and manage accounts and entitlements in SAP Fieldglass 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. > [!NOTE] > > - Create and Update Account is applicable for Buyer users only. > - Provisioning Operations are applicable for Buyer users only. ## Default Create Account Attributes | Account Attribute | Description | | --- | --- | | Login Name | A unique identifier for the user. This is a mandatory attribute. | | First Name | The first name of the user. | | Last Name | The last name of the user. | | Display Name | The display name of the user. | | Login Authentication Type | The login authentication type. | | Manager | The id of the user. | | Division | The primary business unit of the user. | ## Update Account Attributes > [!NOTE] > > There are no mandatory parameters for Update Account. The following is a list of supported attributes that are verified. ### Provisioning Policy Attributes | Account Attribute | Description | | --- | --- | | First Name | The first name of the user. | | Last Name | The first, middle, and last name of the user. | | Email | The email address of the user. | | Manager | The user's supervisor's Id. | | Division | The primary business unit of the user. | | Login Auth Type | The login authentication type of the user. Currently we are supporting 'Password' only. | ### Additional OOTB Attributes | Account Attribute | Description | | --- | --- | | Employee ID | The employee number of the user. | | Phone Number | The phone number of the user. | | Deactivation Date | The deactivation date of the user. | | Street Address | The address of the user (Address 1 field of SAP Fieldglass). | | Country | The country of the user. The country should be updated along with the street address. | | Postal Code | The postal code of the user. | | Job Title | The job title of the user. | | TimeZone | The timezone of the user. | ### Additional Attributes | Account Attribute | Description | | --- | --- | | Currency | The currency of the user. | | Mobile Number | The mobile number of the user. | | Language | The language preference of the user. | | City | The city of the user. | | Cost Center Access\* | The cost center the user has access to. \*Add the display name of this attribute in the schema as well as in report's display name field. | | Site Access\* | The site the user has access to. \*Add the display name of this attribute in the schema as well as in report's display name field. | | Business Unit Access\* | The business unit the user has access to. \*Add the display name of this attribute in the schema as well as in report's display name field. | > [!NOTE] > > - For information on the configuration of additional attributes, refer to [Configure Additional Attributes via Report]() and [Configure Additional Attributes with SCIM](). > - SCIM configuration for attributes is supported with SCIM API. # 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 SAP Fieldglass 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 SAP Fieldglass SaaS source, the default correlation mapping is: | Account Attribute | Operation | Identity Attribute | | --- | --- | --- | | Email | Equals | Work Email | | Login Name | Equals | Username | ## 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 SAP Fieldglass 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 | A unique identifier for the user. | | Login Name | The user's login name or user name. | | Active | The user's active status. | | First Name | The user's first name. | | Last Name | The user's last name. | | Display Name | The user's display name. | | Formatted Name | The user's formatted name. | | User Type | The type of user. | | Email | The user's work email address. | | Manager | The primary manager of the user. | | Country | The user's Country, expressed as a two-letter country code. | | Postal Code | The user's ZIP or postal code. | | Region | The user's state or region. | | Street Address | The user's street name. | | Phone Number | The user's primary phone number. | | Timezone | The user's timezone. | | Deactivation Date | The user's termination/end date. | | Employee ID | The user's employee number. | | Organization | The user's organization. | | Job Title | The user's job title. | | Cost Center | The user's cost center. | | Division | The user's primary business unit. | | Legal Entity | The user's legal entity. | | Login Authentication Type | The user's login authentication type. | | Universally Unique Identifier | The user's universally unique identifier. | #### Worker Specific Attributes | Attribute Name | Description | | --- | --- | | Worker currency | The worker's currency. | | Worker ID | The worker's ID. | | Worker Work Order Id | The worker's work order ID. | | Worker Work Order Start Date | The worker's work order start date. | | Worker Work Order End Date | The worker's work order end date. | | Worker Start Date | The worker's start date. | | Worker End Date | The worker's end date. | | Worker Type | The worker's type. | | Worker External Reference ID | The worker's external reference ID. | | Supplier Name | The worker's supplier name. | | Future Actions | Information about Future Worker in JSON 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. ### Default Role Attributes The SAP Fieldglass SaaS connector supports roles. The following attributes must be configured on the managed system and in the SailPoint source schema to manage roles. #### Primary Role | Attribute Name | Description | | --- | --- | | ID | A unique identifier for the role. | | Display Name | The role's full name. | #### Additional Role | Attribute Name | Description | | --- | --- | | ID | A unique identifier for the role. | | Display Name | The role's full name. | # 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](). ## Warning while Performing Provisioning Operations `Record 1:warning:The Display Name specified is already in use by another person in your company. Please specify a different value.` **Resolution**: Ensure the user's Display Name is unique. If it isn't unique you must update it from the Fieldglass managed system. ## Error - Text 'Date' could not be parsed: Invalid value for MonthOfYear (valid values 1 - 12): 13s This error typically occurs when the date format is incorrect. **Resolution**: Ensure that the User Preferences date format is set to MM/DD/YYYY. To update the date format, follow these steps: 1. Log in to the Fieldglass system using Configuration Manager credentials. 2. Click on the User icon, then select My Preferences. 3. Click Edit, and update the Date Format to MM/DD/YYYY. 4. Save the changes. ## Enable or Disable Account Fails with 404 Not Found **Issue**: Enable or disable account fails with a 404 Not Found error when provisioning policies are active. The connector sends a get account request that repeats the API version in the Host URL. For example, `/api/v1/api/v1/Users/`. **Resolution**: Set `fixDuplicateApiVersionInHostUrl` to `true` on the source. The default value is `false`. **To update the source:** 1. Send a PATCH request with the [Update Source]() API for the source. 2. Use the following request body: ```text [ { "op": "add", "path": "/connectorAttributes/fixDuplicateApiVersionInHostUrl", "value": true } ] ``` 3. Retry the enable or disable operation.