# SailPoint Guidewire ClaimCenter SaaS Connector Documentation > Guidewire ClaimCenter SaaS Connector Documentation # Documentation # Connecting SailPoint and Guidewire ClaimCenter SaaS To connect SailPoint with Guidewire ClaimCenter, 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 Provide the information required to connect and interact with the source. > [!NOTE] > > **Screenshot** > > [![Connection Settings]()]() 1. Enter the **Host URL** path used to connect to the Guidewire ClaimCenter SaaS system. 2. Select an **Authentication Type**. ### Basic > [!NOTE] > > **Screenshot** > > [![Basic authentication settings]()]() 1. Select **Basic** as the authentication type. 2. Enter the **Username** of the Guidewire ClaimCenter SaaS instance with the appropriate permissions to manage the source. 3. Enter the **Password** to authenticate with the Guidewire ClaimCenter SaaS instance. ### OAuth 2.0 > [!NOTE] > > **Screenshot** > > [![OAuth 2.0 authentication settings]()]() 1. Select **OAuth 2.0** as the authentication type. 2. Select a **Grant Type** for OAuth 2.0 authentication as Client Credentials. 3. Enter the **Token URL** for generating the access token. For example, `https://{yourOktaDomain.com}/oauth2/{authorizationServerId}/v1/token`. 4. Enter the **Client ID** and **Client Secret** used for OAuth 2.0 authentication. 5. Enter the **Scope** that the connector should include while requesting an access token for certain operations. Separate multiple scopes with a space. 6. Select **Save**. ## Aggregation Settings Provide the following settings requirement for aggregation. For more information about aggregation, refer to [Loading Account Data](). > [!NOTE] > > **Screenshot** > > [![Aggregation Settings]()]() 1. Enter filter conditions in the **Account Filter** to define the scope of the account aggregation process. For example, `username:eq:sail`. 2. Enter filter conditions in the **Group Filter** to define the scope of the groups to include in entitlement aggregation processes. For example, `name:sw:pc`. 3. Enter filter conditions in the **Role Filter** to define the scope of the roles to include in entitlement aggregation processes. For example, `name:eq:role`. 4. Enter the number of records in the **Page Size** to aggregate in a single page when iterating over large datasets. You can enter from 1 to 100. The default is 100. 5. Select **Save**. > [!NOTE] > > For more details on Guidewire filters, refer to the respective Guidewire ApplicationCenter's [Cloud API Consumer Guide](). ## Provisioning Settings Configure settings related to provisioning operations. > [!NOTE] > > **Screenshot** > > [![Provisioning Settings]()]() 1. Enter the **Work Phone Country Code** to add to users' work phone details. For example, `IN` for India or `US` for USA. 2. 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 Guidewire ClaimCenter SaaS > [!NOTE] > > **Integration** > > This is an integration and requires additional licensing or subscriptions to utilize it. For more information, contact your customer success manager. This guide is designed to give specific information about the requirements and field definitions needed to get a working instance of a Guidewire ClaimCenter SaaS connector in SailPoint. Guidewire ClaimCenter is a claims management system for insurance companies. It provides a comprehensive platform for managing the claim lifecycle, from first notice of loss through investigation and evaluation to settlement and payment. You can manage users, groups, and roles. > [!NOTE] > > To view the latest features, enhancements, and fixes for all SaaS connectors, refer to the [SaaS Release Notes]() page. ## Supported Features The Guidewire ClaimCenter SaaS connector supports the following features: ### Account Management - Manage Users as Accounts - Aggregate Users - Read, Create, Update, and Delete - Enable/Disable User ### Group Management - Read Entitlements (Group and Role) - Add/Remove Entitlements (Group and Role) from the User - Aggregate Entitlements (Group and Role) ## Prerequisites - Guidewire ClaimCenter SaaS can only connect from a trusted IP address. Within Atlas, you must create a list of trusted IP addresses that can be used to connect to a source and access the data. For more information, refer to [IP Address Allow List]() in the SailPoint Developer Community documentation. - Know the authentication option (OAuth 2.0 Authentication) to use for SailPoint to authenticate. - [Configure SailPoint for provisioning](). - Obtain OAuth credentials from Guidewire Cloud Support team. > [!IMPORTANT] > > You must obtain OAuth credentials from the Guidewire Cloud Support team. After you receive the OAuth credentials, ensure that a `role.yaml` file is present in the Guidewire ClaimCenter SaaS environment, and then add the required endpoints mentioned in [Required Permissions](<#required-permissions>). ## Required Permissions - A user with access to the following operations is required: - `GET: /users` - `POST: /users` - `PATCH: /users/{userId}` - `DELETE: /users/{userId}` - `GET: /groups` - `GET: /groups/{groupId}` - `GET: /groups/{groupId}/users` - `POST: /groups/{groupId}/users` - `DELETE: /groups/{groupId}/users/{groupUserId}` - `GET: /groups/{groupId}/users/{groupUserId}` - `PATCH: /groups/{groupId}/users/{groupUserId}` - `GET: /roles` - `GET: /roles/{roleId}` - A user with read-only access requires the following operations: - `GET: /users` - `GET: /groups` - `GET: /groups/{groupId}` - `GET: /groups/{groupId}/users` - `GET: /groups/{groupId}/users/{groupUserId}` - `GET: /roles` - `GET: /roles/{roleId}` ## Supported Managed Systems The SailPoint Guidewire ClaimCenter SaaS connector supports the following releases of the Guidewire ClaimCenter application: - The Olos release is identified by the 2025.11 release number, with application version 50.15.x. - The Niseko release is identified by the 2025.07 release number, with application version 50.14.x. - The Mammoth release is identified by the 2025.03 release number, with application version 50.13.x. > [!NOTE] > > For more information, refer to [Guidewire Documentation](). # Machine Account Attributes ## Machine Account Provisioning Attributes Machine account creation uses the same attribute keys as standard account creation, but uses different generators. The following table lists the machine account creation attributes. | Attribute | Display Name | Type | Required | Generator | Description | | --- | --- | --- | --- | --- | --- | | username | Username | string | No | Static | The user's unique name. Enter a unique username for the machine account. | | firstName | firstName | string | No | Static | The user's first name. | | lastName | lastName | string | No | Static | The user's last name. | | active | active | boolean | No | Static | The user's active status. | | employeeNumber | employeeNumber | string | No | Static | The employee number assigned to the user. | | vacationStatus | vacationStatus | string | Yes | Static | The user's vacation status. For example: atwork, onvacation, inactive. | | workPhoneCountryCode | workPhoneCountryCode | string | No | Disable | The user's work phone country code. | | workPhoneNumber | workPhoneNumber | string | No | Disable | The user's work phone number. | ### Classification The Classification attribute is used to identify and categorize the account as a Machine Account. - **Attribute name** - UserType - **Value** - Communication, Reference, Service, System For more information, refer to [Machine Identity Security Overview](). # Provisioning The Guidewire ClaimCenter SaaS connector supports provisioning, allowing you to create and manage accounts and entitlements in Guidewire ClaimCenter 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 | Account Attribute | Type | Generator | Description | | --- | --- | --- | --- | | username | String | Identity Attribute - SailPoint User Name (uid) | The user's username. | | firstName | String | Identity Attribute - Given Name (firstname) | The user's first name. | | lastName | String | Identity Attribute - Family Name (lastname) | The user's last name. | | active | Boolean | Static | The user's active status. | | employeeNumber | String | Identity Attribute - Employee Number (identificationNumber) | The employee number assigned to the user. | | vacationStatus | String | Static | The user's vacation status. For example: atwork, onvacation, inactive. | | workPhoneCountryCode | String | Disable | The user's work phone country code. | | workPhoneNumber | String | Disable | The user's work phone number. | | companyName\_Ext | String | Static | The user's company typelist value. Provide the typelist code. For example: CGIC. | | externalCompany\_Ext | String | Static | The user's external company typelist value. Provide the typelist code. For example: EXTCO. | | language\_Ext | String | Static | The user's language typelist value. Provide the typelist code. For example: en\_CA. | | state\_Ext | String | Static | The user's state or province typelist value. Provide the typelist code. For example: ON. | | country\_Ext | String | Static | The user's country typelist value. Provide the typelist code. For example: CA. | | hrSupervisor\_Ext | String | Static | The user's HR supervisor reference value. Provide the Guidewire user id. For example: cc:18304. | # 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 Guidewire ClaimCenter 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 Guidewire ClaimCenter SaaS source, the default correlation mapping is: | Account Attribute | Operation | Identity Attribute | | --- | --- | --- | | username | Equals | SailPoint Username (uid) | | displayName | Equals | Display Name (displayName) | ## 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 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 | | --- | --- | | id | Account | | id | Group | | id | Role | ### Default Account Attributes The Guidewire ClaimCenter 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 identifier. This is an Account ID which must not be changed. | | username | The user's username. | | firstName | The user's first name. | | lastName | The user's last name. | | suffix | The user's suffix as applicable. | | active | The user's active status. Type: Boolean. | | externalUser | Indicates if the user is from an organization external to the insurer organization. Type: Boolean. | | displayName | The user's formatted name. | | employeeNumber | The employee number assigned to the user. | | vacationStatus | The user's vacation status. For example: atwork, onvacation, inactive. | | workPhoneCountryCode | The user's work phone country code. | | workPhoneNumber | The user's work phone number. | | authorityLimitProfile | The authority limit profile assigned to the user. | | groups | The group(s) that the user belongs to. Type: group. Properties: Entitlement, Multi-Valued. | | roles | The role(s) that have been granted to the user. Type: role. Properties: Entitlement, Multi-Valued. | | companyName\_Ext | The user's company typelist value. Expected value semantics: typelist code. | | externalCompany\_Ext | The user's external company typelist value. Expected value semantics: typelist code. | | language\_Ext | The user's language typelist value. Expected value semantics: typelist code. | | state\_Ext | The user's state/province typelist value. Expected value semantics: typelist code. | | country\_Ext | The user's country typelist value. Expected value semantics: typelist code. | | hrSupervisor\_Ext | The user's HR supervisor reference value. Expected value semantics: user id. | ## 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 Group Attributes The Guidewire ClaimCenter SaaS connector also supports groups. The following attributes must be configured on the managed system and in the SailPoint source schema to manage groups. | Attribute Name | Description | | --- | --- | | id | The group's unique identifier. This is an Entitlement ID which must not be changed. | | name | The group's name. This is an Entitlement Name which must not be changed. | | displayName | The group's formatted name. | | groupType | The group's type. | | parent | The group's parent group. | | securityZone | The group's security zone. | | supervisor | The name of the group supervisor. | ### Default Role Attributes The Guidewire ClaimCenter SaaS connector supports roles. The following attributes must be configured on the managed system and in the SailPoint source schema to manage roles. | Attribute Name | Description | | --- | --- | | id | The role's unique identifier. This is an Entitlement ID which must not be changed. | | name | The role's name. This is an Entitlement Name which must not be changed. | | carrierInternal | Indicates if the role is applicable to internal carrier organization users. Type: Boolean. | | description | A detailed description of the role. | | displayName | The formatted name of the role. | # 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]().