# SAP Commerce Cloud SaaS Connector > SailPoint SAP Commerce Cloud SaaS Connector Documentation # Documentation # Connecting SailPoint and SAP Commerce Cloud SaaS To connect SailPoint with SAP Commerce Cloud, 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 The following information is required for SailPoint to connect and interact with SAP Commerce Cloud SaaS. > [!NOTE] > > **Screenshot** > > [![Connection Settings]()]() 1. Select **Connection Settings** from the menu. 2. In **Base URL**, enter the host URL of the SAP Cloud Identity Services Tenant. 3. In **System ID**, enter the ID of the IPS Proxy Source for SAP Commerce Cloud. 4. In **Client ID** and **Client Secret**, enter the SAP IPS technical user credentials as mentioned in the [Prerequisites](). 5. Enter the **Page Size** as the number of records to fetch in one request. The default is 100. Supported values are 10 to 100. 6. 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 Commerce Cloud SaaS > [!NOTE] > > **Integration** > > This is an integration and requires additional licensing or subscriptions to utilize it. For more information, contact your customer success manager. The SAP Commerce Cloud SaaS connector offers access management of SAP Commerce 'Employees' type users, group entitlements, and rich attribute collection as supported by SAP. This guide is designed to give specific information about the requirements and field definitions needed to get a working instance of a source in SailPoint. > [!NOTE] > > This integration of the SAP Commerce Cloud SaaS connector has been built using SAP Identity Provisioning Services (IPS). The credentials used to connect to SAP Commerce Cloud are the same for SAP Identity Provisioning Services. > [!NOTE] > > To view the latest features, enhancements, and fixes for all SaaS connectors, refer to the [SaaS Release Notes]() page. ## Supported Features The SAP Commerce Cloud 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 for User Type "Employee" - Groups Aggregation for User Group Type "Scim" - Add/Remove Entitlement (Group) - Account Provisioning - Create User - Update User - Enable/Disable User - Delete User For more information on features, refer to [Source Features](). ## Supported Managed System - SAP Commerce Cloud standard edition. ## Prerequisites - The following set of credentials must be created to configure the IPS Proxy of the SAP Commerce Cloud SaaS connector and connect to SailPoint to allow it to handle associated identity governance use cases. - Obtain a Bundle Tenant. To get identity provisioning services, refer to [Initial Setup of Bundle Tenants]() in the SAP Help Portal. ### Configure OAuth Client for SAP Commerce Cloud SaaS The necessary permissions are required to create the OAuth client. 1. Sign in to the SAP Commerce Cloud system and from the side navigation menu, go to **System \> OAuth** tab. 2. Under **Configured Clients**, select **Add a New OAuth Client**. In the dialog, provide the following details: - **OAuth Client ID**: Specify an ID for the OAuth client. For example: `my300xxx` - **OAuth authorities**: Specify value as `ROLE_SCIM_CLIENT`. - **OAuth authorized grant types**: Specify value as `OAuth authorized grant types`. - **Scopes**: Specify value as basic and extended. - Select **Save**. ### Configure the Technical User in SAP Identity Provisioning Service (IPS) 1. To enable basic authentication, sign in to the SAP Cloud Identity Services admin console, and go to **Users and Authorizations \> Administrators**. 2. Add an administrator user of the type `System`, and then provide the name of the user. 3. In **Configure Authorizations**, select the **Access Proxy System API** permission, and then **Save**. 4. Go to **Configure System Authentication \> Secrets \> Add**, and copy the **Client Secret** and **Client ID**. These are the technical user credentials that you will use to communicate with SAP Commerce Cloud. ### Configure the SAP Identity Provisioning Service Proxy System Use one of the following options to configure the proxy system. SailPoint recommends using the import file template. > [!NOTE] > > **Option 1 - Use the import file template** > > 1. Sign in to the SAP Cloud Identity Services admin console. Go to **Identity Provisioning \> Proxy Settings**, and select the **\+Add** button. > 2. Download the provided template, edit the placeholders with the appropriate property values, and save the changes. > > ```json > { > "id": "a8887106-dec8-4ffa-80e7-fc5b978838c5", > "connectorTypeString": "SAP_COMMERCE_CLOUD", > "accessMode": "PROXY", > "destinationName": "", > "gitAllowedExpressions": [], > "gitDisallowedExpressions": [], > "emailSubscribers": [], > "name": "ANANDTESTNG", > "tenantId": "avbxg9a02", > "state": "ENABLED", > "systemManagementType": "CUSTOMER_MANAGED", > "properties": { > "Authentication": "BasicAuthentication", > "ips.trace.failed.entity.content": "false", > "OAuth2TokenServiceURL": "https://backoffice.cpisimpxeb-sailpoint1-d1-public.model-t.cc.commerce.ondemand.com/authorizationserver/oauth/token", > "ProxyType": "Internet", > "Type": "HTTP", > "URL": "https://backoffice.cpisimpxeb-sailpoint1-d1-public.model-t.cc.commerce.ondemand.com", > "User": "anand" > }, > "encryptedProperties": { > "Password": null > }, > "automaticOutboundCertificateRenew": false, > "transformationChanged": false, > "readTransformationChanged": true, > "writeTransformationChanged": false, > "fromImport": false, > "readTransformation": { > "user": { > "mappings": [ > { > "sourcePath": "$.id", > "targetPath": "$.id", > "targetVariable": "entityIdSourceSystem" > }, > { > "sourcePath": "$.userName", > "optional": true, > "targetPath": "$.userName" > }, > { > "sourceVariable": "entityBaseLocation", > "targetPath": "$.meta.location", > "targetVariable": "entityLocationSourceSystem", > "functions": [ > { > "function": "concatString", > "suffix": "${entityIdSourceSystem}" > } > ] > }, > { > "sourcePath": "$.schemas", > "preserveArrayWithSingleElement": true, > "targetPath": "$.schemas" > }, > { > "sourcePath": "$['urn:ietf:params:scim:schemas:extension:sap:2.0:User']['userUuid']", > "optional": true, > "targetPath": "$['urn:ietf:params:scim:schemas:extension:sap:2.0:User']['userUuid']" > }, > { > "sourcePath": "$.externalId", > "optional": true, > "targetPath": "$.externalId" > }, > { > "sourcePath": "$.displayName", > "optional": true, > "targetPath": "$.displayName" > }, > { > "sourcePath": "$.nickName", > "optional": true, > "targetPath": "$.nickName" > }, > { > "sourcePath": "$.name.familyName", > "optional": true, > "targetPath": "$.name.familyName" > }, > { > "sourcePath": "$.name.middleName", > "optional": true, > "targetPath": "$.name.middleName" > }, > { > "sourcePath": "$.name.givenName", > "optional": true, > "targetPath": "$.name.givenName" > }, > { > "sourcePath": "$.name.honorificSuffix", > "optional": true, > "targetPath": "$.name.honorificSuffix" > }, > { > "sourcePath": "$.addresses", > "preserveArrayWithSingleElement": true, > "optional": true, > "targetPath": "$.addresses" > }, > { > "sourcePath": "$.userType", > "optional": true, > "targetPath": "$.userType" > }, > { > "sourcePath": "$.active", > "optional": true, > "targetPath": "$.active" > }, > { > "sourcePath": "$.emails", > "preserveArrayWithSingleElement": true, > "optional": true, > "targetPath": "$.emails" > }, > { > "sourcePath": "$.groups", > "preserveArrayWithSingleElement": true, > "optional": true, > "targetPath": "$.groups" > } > ], > "scimEntityEndpoint": "Users" > }, > "group": { > "mappings": [ > { > "sourcePath": "$.id", > "targetPath": "$.id", > "targetVariable": "entityIdSourceSystem", > "correlationAttribute": true > }, > { > "sourceVariable": "entityBaseLocation", > "targetPath": "$.meta.location", > "targetVariable": "entityLocationSourceSystem", > "functions": [ > { > "function": "concatString", > "suffix": "${entityIdSourceSystem}" > } > ] > }, > { > "sourcePath": "$.schemas", > "preserveArrayWithSingleElement": true, > "targetPath": "$.schemas" > }, > { > "sourcePath": "$.displayName", > "targetPath": "$.displayName" > }, > { > "sourcePath": "$.members", > "preserveArrayWithSingleElement": true, > "optional": true, > "targetPath": "$.members" > } > ], > "scimEntityEndpoint": "Groups" > } > }, > "writeTransformation": { > "user": { > "mappings": [ > { > "sourceVariable": "entityIdTargetSystem", > "targetPath": "$.id" > }, > { > "sourcePath": "$.userName", > "targetPath": "$.userName" > }, > { > "sourcePath": "$.schemas", > "preserveArrayWithSingleElement": true, > "targetPath": "$.schemas" > }, > { > "sourcePath": "$['urn:ietf:params:scim:schemas:extension:sap:2.0:User']['userUuid']", > "optional": true, > "targetPath": "$['urn:ietf:params:scim:schemas:extension:sap:2.0:User']['userUuid']" > }, > { > "sourcePath": "$.externalId", > "optional": true, > "targetPath": "$.externalId" > }, > { > "sourcePath": "$.displayName", > "optional": true, > "targetPath": "$.displayName" > }, > { > "sourcePath": "$.nickName", > "optional": true, > "targetPath": "$.nickName" > }, > { > "sourcePath": "$.name.familyName", > "optional": true, > "targetPath": "$.name.familyName" > }, > { > "sourcePath": "$.name.middleName", > "optional": true, > "targetPath": "$.name.middleName" > }, > { > "sourcePath": "$.name.givenName", > "optional": true, > "targetPath": "$.name.givenName" > }, > { > "sourcePath": "$.name.honorificSuffix", > "optional": true, > "targetPath": "$.name.honorificSuffix" > }, > { > "condition": "($.addresses[*].region EMPTY false) && ($.addresses[*].country EMPTY false)", > "sourcePath": "$.addresses", > "preserveArrayWithSingleElement": true, > "optional": true, > "targetPath": "$.addresses", > "functions": [ > { > "type": "convertCountryRegion", > "outputFormat": "alpha2", > "inputAttributes": [ > "region", > "country" > ], > "outputAttribute": "region" > } > ] > }, > { > "sourcePath": "$.userType", > "optional": true, > "targetPath": "$.userType" > }, > { > "sourcePath": "$.active", > "optional": true, > "targetPath": "$.active" > }, > { > "sourcePath": "$.emails", > "preserveArrayWithSingleElement": true, > "optional": true, > "targetPath": "$.emails" > }, > { > "sourcePath": "$.groups[*].value", > "preserveArrayWithSingleElement": true, > "optional": true, > "targetPath": "$.groups[?(@.value)]" > }, > { > "constant": "urn:ietf:params:scim:api:messages:2.0:PatchOp", > "targetPath": "$.schemas[0]", > "scope": "patchEntity" > }, > { > "sourcePath": "$.Operations", > "preserveArrayWithSingleElement": true, > "targetPath": "$.Operations", > "scope": "patchEntity" > } > ], > "scimEntityEndpoint": "Users" > }, > "group": { > "mappings": [ > { > "sourceVariable": "entityIdTargetSystem", > "targetPath": "$.id" > }, > { > "sourcePath": "$.displayName", > "optional": true, > "targetPath": "$.displayName" > }, > { > "constant": "urn:ietf:params:scim:schemas:core:2.0:User", > "targetPath": "$.schemas[0]" > }, > { > "sourcePath": "$.Operations", > "preserveArrayWithSingleElement": true, > "targetPath": "$.Operations", > "scope": "patchEntity" > }, > { > "sourcePath": "$.schemas", > "preserveArrayWithSingleElement": true, > "targetPath": "$.schemas", > "scope": "patchEntity" > }, > { > "sourcePath": "$.members[*].value", > "preserveArrayWithSingleElement": true, > "optional": true, > "targetPath": "$.members[?(@.value)]" > } > ], > "scimEntityEndpoint": "Groups" > } > }, > "gitFetchAllowed": false > } > ``` > 3. Select **Import File**, and browse to the downloaded file. > [!NOTE] > > **Option 2 - Use the manual process** > > Follow the manual process provided on [SAP Help Portal](). ## Required Permissions The following permissions are required for the OAuth client and Technical user (IPS): - SAP Commerce Cloud (to configure the OAuth client) - OAuth client can be created by the system user - SAP Identity Provisioning Service (to configure technical user) - The technical user is required to be created by the tenant administrator. Select the **Access Proxy System API** permission in **Configure Authorizations**. # 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 Commerce Cloud 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 Commerce Cloud SaaS source, the default correlation mapping is: | Account Attribute | Operation | Identity Attribute | | --- | --- | --- | | User Name | Equals | Username | | Email | Equals | Work Email | ## 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 Commerce Cloud 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. | | Active | The user's active status. | | Login Name | The user's login name or user name. | | First Name | The user's first name. | | Last Name | The user's last name. | | Display Name | The user's display name. | | email | The user's work email address. | | External ID | The user's External ID. | | Groups | Name of Groups to which the admin user is connected to. | ## 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 SAP Commerce Cloud 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 | | --- | --- | | Name | The name of the group. | | ID | The ID of the group. | # 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]().