# SailPoint SAP S/4HANA Cloud Connector Documentation > SAP S/4HANA Cloud Connector Documentation # Documentation # Connecting SailPoint and SAP S/4HANA Cloud To connect SailPoint with SAP S/4HANA 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. Select **Virtual Appliance**. A virtual appliance is a Linux-based virtual machine that connects to your sources and apps using SailPoint APIs, connectors, and integrations. For more information about configuring and deploying virtual appliances, refer to [SailPoint Virtual Appliances](). 4. (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](). 5. Configure the authentication to allow SailPoint to connect to the source. For more information, refer to the **Connection Settings** section. 6. 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. Under **Connection Type**, select **Direct Connection** or **Flat File**. - **Direct Connection** - A direct connection fetches data from the **Virtual Appliance Cluster** you choose as the application connector for the source. A direct connection configuration allows for real-time updates. For more information about configuring and deploying virtual appliances, refer to the [Virtual Appliance Reference Guide](). - **Flat File** - Select the flat file if no connector is available, or if another system restricts the connection. This option allows only reading and aggregating data as a generic/delimited application. Provisioning activity is unsupported, and additional configuration pages like connection settings and aggregation settings are unavailable. 5. If you selected **Direct Connection**, in **Virtual Appliance Cluster**, select the virtual appliance cluster that will be used as the application connector for the source. 6. (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](). 7. 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](). 8. 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. In the **Virtual Appliance Cluster** dropdown list, select the virtual appliance to use when communicating with your organization's systems. For more information, refer to [SailPoint Virtual Appliances](). 4. (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](). 5. Configure the authentication to allow SailPoint to connect to the source. Refer to [Connection Settings](<#connection-settings>) for more information. 6. (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](). 7. (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. 8. Select **Save**. ### Connector Files > [!NOTE] > > **Screenshot** > > [![Connector Files]()]() 1. Select **Upload Files** to upload the role details file that you want to use for the source. The role details must be exported in a .csv file. > **Warning** > > Ensure that the file you upload is not vulnerable or malicious. > **Note** > > You must download the library from a trusted source and validate the authenticity of the download location via inspection of valid SSL/TLS certificates. You must also validate the authenticity of the library by inspecting digital signatures or validating checksums when that information is made available. 2. Select **Save**. ## Connection Settings > [!NOTE] > > **Screenshot** > > [![Connection Settings]()]() 1. Select **Connection Settings** from the menu. 2. Enter the **API URL**. This is the Service URL of the endpoint to be used. For example, `https://.com` 3. Enter the **User name**. This is the name of the Communication User with required permission connecting to the SAP S/4HANA Cloud system. 4. Enter the associated **Password**. 5. Select **Save**. ## Aggregation Settings For more information about aggregation, refer to [Loading Account Data](). > [!NOTE] > > **Screenshot** > > [![Aggregation Settings]()]() 1. Select **Aggregation Settings** from the menu. 2. Enable **Direct Role Aggregation** toggle button to enable to use SCIM API in order to fetch the roles from S4 HANA public cloud. 3. Enter the **Role Details File Name** that has the details of roles Business UUID and Business ID. 4. In **Page Size**, enter the number of records to fetch. The default value is 50. 5. Select **Save**. ## Provisioning Settings Configure settings for provisioning operations between the connector and the source. > [!NOTE] > > **Screenshot** > > [![Provisioning Settings]()]() 1. Select **Create Business User Account** toggle button to enable the creation of business user account on S/4HANA public cloud. 2. Enter the API URL in **Worker ID API** for detecting the Worker based on the FirstName, LastName and Email. When not provided, Worker ID needs to be passed in provisioning plan to create the Business User on S4 HANA public cloud. 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 S/4HANA Cloud > [!NOTE] > > **Integration** > > This is an integration and requires additional licensing or subscriptions to utilize it. For more information, contact your customer success manager. SAP S/4HANA is an Enterprise Resource Planning (ERP) Business Suite based on the SAP HANA in-memory database with which transactions and business data analysis can be performed in real time. This guide is designed to give specific information about the requirements and field definitions needed for SAP S/4HANA Cloud. > [!NOTE] > > To view the latest features, enhancements, and fixes for all SaaS connectors, refer to the [SaaS Release Notes]() page. ## Supported Features SAP S/4HANA Cloud supports the following features: - Aggregation of SAP S/4HANA Business Users as Accounts - Add/Remove Entitlements (supported entitlements are Business Roles) - Enable/Disable SAP S/4HANA Cloud accounts - Aggregation of Business Role as Account-Group - Create Business User Account on S/4HANA Cloud > **Note** > > Create Business User is supported for user type "Employee" (BUP003). - Update User Attributes (User Date Valid From and User Date Valid To) Refer to [Source Features]() for more information on features. Contact your CSM or SailPoint [Services]() for feature settings. > [!NOTE] > > The S/4HANA Cloud Connector now supports direct role aggregation using the SCIM API. To migrate from file-based aggregation to direct aggregation, refer to [Migration from CSV Role Aggregation to Direct Role Aggregation](<#migration-from-csv-role-aggregation-to-direct-role-aggregation>). ### 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** > > [![Privilege Level - High]()]() > > [![Privilege Level - Medium]()]() ## Prerequisites - Configure at least one virtual appliance cluster and successfully test the connection. Refer to the [Virtual Appliance Reference Guide]() for instructions. - Create the Communication User, Communication System, and Communication Arrangement on the SAP system, and export Role Data for SAP S/4HANA Cloud. - The role details must be exported in a .csv file. ### File Upload Utility The file upload utility provides a way for you to upload files to the cloud automatically. For more information about downloading and using the file upload utility with the SAP S/4HANA Cloud source, refer to [File Upload Utility](). ### Create Communication User A Communication User is a user defined in the SAP S/4HANA Cloud system for inbound communication and processing messages in the system. 1. Sign in as an administrator to the SAP S/4HANA Cloud system. In the **Communication Management** panel, select **Maintain Communication Users**. A list of existing communication users page is displayed. 2. To create a new communication user, select **New**. 3. Enter the following details and select **Create**: - User Name\* - Description\* - Password 4. Note the details of the User Name and Password used above. ### Create Communication System A Communication system is defined in the SAP S/4HANA Cloud system as a target system. Communication systems must be created for inbound and outbound communication. 1. Sign in as an administrator to the SAP S/4HANA Cloud system. In the **Communication Management** panel, select **Communication Systems**. A list of existing communication systems page is displayed. 2. To create a new communication system, select **New**. 3. Enter the following details, and select **Create**: - System ID\* - System Name\* 4. For inbound communication, perform the following: 1. Enter the details for the **Host Name\***. 2. In the **User for Inbound Communication** panel, select **Add (+)** to add a new user. 3. Select an **Authentication Method** from the dropdown list, specify a relevant **User Name**, and select **OK**. 5. For outbound communication, perform the following: 1. In the **User for Outbound Communication** panel, select an **Authentication Method** from the dropdown list and specify the **User Name** and **Password**. 2. Select **Create**. 6. Select **Save** to complete the creation of the communication system. ### Create Communication Arrangement Communication Arrangement is defined in the SAP S/4HANA Cloud system to enable key users to create and edit communication arrangements that are set up with a communication partner. 1. Sign in as an administrator to the SAP S/4HANA Cloud system. In the **Communication Management** panel, select **Communication Arrangements**. A list of existing communication arrangements page is displayed. 2. To create a new communication arrangement, select **New**. 3. Enter the following details and then select **Create**: - Scenario\* - The Scenario ID is **SAP\_COM\_0093** and **SAP\_COM\_0465** - Arrangement Name 4. Select the ID of the **Communication System\*** and enter other details. 5. Select **Save** to complete the creation of a communication arrangement. #### Obtaining the URL Details The existing list of Communication Arrangements page is updated to include the newly created communication arrangement for the **SAP\_COM\_0093** and **SAP\_COM\_0465** scenario as explained above. To obtain the URL details, perform the following: 1. Select the newly created communication arrangement with Scenario ID **SAP\_COM\_0093** and **SAP\_COM\_0465**. The details of the **SAP\_COM\_0093** and **SAP\_COM\_0465** communication arrangement are displayed. 2. Under the **Inbound Services** section, copy the URL mentioned in **Service URL/Service Instance**. ### Create Business User Account The S/4HANA Cloud system supports the creation of Business User accounts. A key requirement for creating a Business User is the presence of a Worker ID. The Worker ID must be passed when creating the user. Additionally, you can use the custom-exposed Worker ID API to fetch worker details from the S/4HANA Cloud system. > [!NOTE] > > The Worker ID API is an optional parameter. If the Worker ID is not known, the Worker ID API can be used to retrieve it. For instructions on obtaining the Worker ID API for your system, refer to [Obtain Worker ID API in S/4HANA Cloud](<#obtain-worker-id-api-in-s4hana-cloud>). > [!NOTE] > > In the S/4HANA Public Cloud, you can only create a Business User Account with a reference to a valid Worker ID. #### Approaches for Creating a Business User in S/4HANA Cloud System 1. Create Business User using Worker ID API - Ensure that the Email ID and Username in the provisioning plan are unique values. - Ensure that the First Name, Last Name, and Email ID in the provisioning plan must be valid to fetch the Worker ID. If both options are provided, Approach B (Passing Worker ID) takes precedence over Approach A (Using Worker ID API). 2. Create Business User using Worker ID This is the standard method for creating a Business User in the S/4HANA Cloud system. - Ensure that the Worker ID, First Name, Last Name, and Email ID in the provisioning plan are appropriate for creating the Business User. #### Obtain Worker ID API in S/4HANA Cloud This is the optional setup process to retrieve the Worker ID from the S/4HANA Cloud System using an API. The Worker ID can be fetched by passing Email, First Name, and Last Name as filters. > [!NOTE] > > This is an optional custom-exposed API that must be explicitly configured in the S/4HANA Cloud system before use. **To configure the Worker ID API:** 1. Create an External API CDS View: - Open the Fiori App for creating custom CDS views (Custom CDS View). - Search for the standard CDS view I\_WorkforcePerson. - Select the following fields: FirstName, LastName, DefaultEmailAddress, PersonFullName, and PersonExternalID. - Select **Publish** to make the view available for use. [![Create Business User]()]() 2. Create a Communication Scenario: - In the Fiori App, create a new Communication Scenario. - Go to **Inbound Services** and add the service generated from the custom CDS view. - Publish the service to make it accessible. 3. Set Up the Communication Arrangement: - Go to Communication Arrangements. Select the Communication Scenario you created earlier. - Enter the required fields such as System and User Name. - Retrieve the generated URL for the communication arrangement. [![Communication Arrangement URL]()]() 4. Configure the Worker ID API in the Connector Settings: - Add the Entity Name (from the API metadata) to the API URL. - Enter the complete URL in the Worker ID API field on the configuration settings page of the connector. ## Required Permissions The following table lists the required permissions for the specific operations mentioned later in this section: | Operation | Required Permissions | | --- | --- | | Test Connection | Test Connection | | Aggregation | Test Connection and Aggregation | | Provisioning | Test Connection, Aggregation and Provisioning | The administrative user must have access to the following Inbound Services to perform the operations: | Operation | Inbound SOAP Services | Service Interface | | --- | --- | --- | | Test Connection /Account Aggregation | Business User - Read | `https:///sap/bc/srt/scs_ext/sap/querybusinessuserin` | | Group Aggregation | Business User - Read | `https:///sap/bc/http/sap/aps_iam_api_scim/Groups` | | Provisioning | Business User - Update | `https:///sap/bc/srt/scs_ext/sap/managebusinessuserin` | | Provisioning | Business User - Update | `https:///sap/bc/http/sap/aps_iam_api_scim/Users` | > [!NOTE] > > After you create the Communication Arrangement SAP\_COM\_0093 and SAP\_COM\_0465 on the SAP managed system and the Communication User is assigned, the service account for the SAP S/4HANA Cloud source will have all the permissions. Refer to [SAP S/4HANA Prerequisites]() for more information. ## Upgrade Considerations SAP has introduced SCIM-based APIs for the S/4HANA Public Cloud, which now support group aggregation. Currently, the connector uses a file-upload based functionality for role aggregation. However, SailPoint recommends migrating to direct role aggregation in the future. Refer to [Migration from CSV Role Aggregation to Direct Role Aggregation](<#migration-from-csv-role-aggregation-to-direct-role-aggregation>) to migrate from file-based aggregation to direct aggregation. ### Schema Attributes for Upgraded Source For Schema Attributes, the following updates are necessary: #### Account Attributes - User Date Valid From - Valid From Date of the Business User - User Date Valid To - Valid To Date of the Business User #### Group Attributes > [!NOTE] > > The Group attributes continue to be Business Role UUID and Business Role ID. ### Create Business User Account For the existing source, manually add a provisioning policy to enable business user account creation. For reference on how to configure the policy, refer to [Create Business User on S/4HANA Cloud Public](). ### Migration from CSV Role Aggregation to Direct Role Aggregation The S/4HANA Cloud Connector now supports direct role aggregation using the SCIM API. > [!CAUTION] > > - Ensure that all necessary backups are taken before starting the migration process. > - Any discrepancies between the CSV file and the S/4HANA Cloud system may result in errors during migration. **To migrate from CSV-based role aggregation to direct role aggregation:** > [!NOTE] > > If the CSV file is already up to date with the correct Business Role count, you can skip obtaining and verifying the CSV file and proceed directly to uploading it. 1. Obtain the latest CSV file from the S/4HANA Public Cloud system. 2. Verify that the business role count in the CSV matches the one in the S/4HANA Cloud system. 3. Go to Base Configuration and upload the latest CSV file. Then, enable the **Direct Role Aggregation** option under Account and Aggregation Settings. Ensure that the Role Details File Name is correct. 4. Save the changes. 5. Perform a Test Connection, followed by Account and Role Aggregation. 6. Once the aggregation is successful, the connector will mark the migration activity as complete. > [!NOTE] > > - If you encounter any issues during the migration process, raise a support ticket for assistance. > - The direct role aggregation process may take some time, depending on the number of roles and accounts. Monitor the progress throughout the aggregation process. > - Once the migration is complete, ensure that the roles and accounts are correctly aggregated in your system. > [!WARNING] > > - The CSV file is required for the initial migration to direct role aggregation. After the migration is complete, the CSV upload method will no longer be supported for role aggregation. > - This change is permanent and aims to streamline the aggregation process moving forward. ## Role Data Export The SAP S/4HANA Cloud connector has the following respective fields in the UI: - (For SailPoint) **Role Details File Name**: Enter the name of the file that has the exported details of the roles. - (For IdentityIQ) **Role Details File Path**: Enter the CSV file path. You can use methods as per your requirement to export the role data that is consistent with the API data. > [!NOTE] > > For Direct Role Aggregation, the export of a CSV file is not required. The following are the Role Data procedure examples for: ### Windows OS (Microsoft Excel) The SAP S/4HANA Cloud connector has the following respective fields in the UI: - For the SailPoint Role Details file name, enter the name of the file that has the details of roles exported for the Windows OS. #### Steps for a Business User with SAP\_CORE\_BC\_IAM\_RM Permission Business Catalogs 1. Sign in to the S/4 HANA cloud tenant, and execute the following query to export results in JSON format: `https:///sap/opu/odata/sap/APS_IAM_BRT_SRV/aps_iam_brt_br?sap-client=100&$format=json&$select=UUID,ID` > **Note** > > You can add more fields to the above URL, separated by commas, to get the dates. The available fields are UUID, TemplateID, LongText, Description, ID, ChangedOn, DifferFromTemplate, and BusinessCatalogAssignmentCount. 2. Save the response in a .json file. 3. Open Microsoft Excel and select **Data \> Get Data \> From JSON**. Browse and select the previously saved .json file. 4. Select **Record**, and then select **List**. > **Screenshot** > > [![Record]()]() > > [![List]()]() 5. Right-click **List**, select **To Table**, and then select **OK**. > **Screenshot** > > [![To Table]()]() > > [![To Table dialog]()]() 6. Select **Column**. Deselect the checkboxes for the columns that are not required, then select **OK**. > **Screenshot** > > [![Column]()]() > > [![Column selection]()]() 7. Verify that the selected column values are rendered. Select **Close & Load**. > **Screenshot** > > [![Close and Load]()]() 8. Rename the **UUID** column to **Business Role UUID**, and rename the **ID** column to **Business Role ID**. 9. Select **File \> Save As**, enter the file name, and select the .csv format for the file type. ### Mac OS (Microsoft Excel) The SAP S/4HANA Cloud connector has the following respective fields in the UI: - For the SailPoint Role Details file name, enter the name of the file that has the details of roles exported for the Windows OS. - Sign in to the S/4HANA Cloud tenant, and execute the following query to export results in the JSON format: `https:///sap/opu/odata/sap/APS_IAM_BRT_SRV/aps_iam_brt_br?sap-client=100&$format=json&$sel...` > **Note** > > You can add more fields to the above URL, separated by commas, to get the dates. Available fields are UUID, TemplateID, LongText, Description, ID, ChangedOn, DifferFromTemplate, and BusinessCatalogAssignmentCount. - Open Microsoft Excel for Mac (License: Office 356 Subscription/ Version 16.32). - In the Excel menu, go to **Insert \> Add-ins \> Get Add-ins**. > **Screenshot** > > [![Get Add-ins]()]() - Search for the **JSON to Excel** add-in, and select **Add**. > **Screenshot** > > [![JSON to Excel add-in]()]() - Select the **JSON to CSV** icon, and copy the **API response JSON**. Paste it into the **Paste your JSON here** field. > **Screenshot** > > [![JSON to CSV]()]() > > [![Paste your JSON here]()]() - Select **Convert** to see the data loaded in the sheet. > **Screenshot** > > [![Convert]()]() - Delete the first three columns and rename the **UUID** column to **Business Role UUID**, and rename the **ID** column to **Business Role ID**. > **Screenshot** > > [![Rename columns]()]() - Go to **File \> Save As** and save the file in .csv format. # Machine Account Attributes Machine account attributes are used in provisioning configurations for machine accounts. After you have [created the required machine account subtypes](), you can use the machine account attributes to provision machine accounts in your SailPoint tenant. Refer to [Machine Identity Security Overview]() for more information. ## Machine Account Provisioning Attributes | Account Attribute | Description | | --- | --- | | First Name | First Name of Business User. | | Last Name | Last Name of Business User. | | Username | Defaults to the identity's user name. | | Email | Email ID of the user. | | Worker ID | Worker ID of the worker of S4HANA system. | > [!NOTE] > > The Worker ID is mandatory if the Worker ID API is not set in the configuration settings. For additional attribute descriptions and provisioning behavior, refer to [Default Create Account Attributes](). # Provisioning The SAP S/4HANA Cloud connector supports provisioning, allowing you to create and manage accounts and entitlements in SAP S/4HANA Cloud 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 > [!NOTE] > > Enable the **Create Business User** checkbox in the configuration settings for Create Operation. | Account Attribute | Description | | --- | --- | | First Name | First Name of Business User. | | Last Name | Last Name of Business User. | | Username | Defaults to the identity's user name. | | Email | Email ID of the user. | | Worker ID | Worker ID of the worker of S4HANA system. | > [!NOTE] > > The `Worker ID` attribute is mandatory if the `Worker ID API` is not set in the configuration settings. ## Modify Support for Attributes | Attribute Name | Type | Modify Supported | Description | | --- | --- | --- | --- | | User Name | String | Yes | Updated through SCIM PATCH. | | User UUID | String | Yes (conditional) | Updated through SCIM PATCH only when `User UUID` exists in the account schema. | > [!NOTE] > > Modify attribute only work when `User Name` and `User UUID` are part of the account schema. # 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 S/4HANA Cloud 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]() 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 | | --- | --- | | Person ID | Account | | Business Role ID | Group | ### Default Account Attributes The SAP S/4HANA Cloud 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 | | --- | --- | | First Name | First Name of Business User. | | Last Name | Last Name of Business User. | | Person External ID | Person External ID of Business User. | | Business Partner Role | Business Partner Role of Business User. | | Person ID | Person ID of Business User. This is an Identity Attribute which must not be changed. | | Email | Email Address of Business User. | | User Name | User Name of Business User. | | User ID | User ID of Business User. | | Employee Date Valid From | Employment start date of the Business User. | | Employee Date Valid To | Employment end date of the Business User. | | Is Locked | Is Business User Locked. | | Business Roles | Business Roles assigned to Business User. | | User Date Valid From | Valid From Date of the Business User. | | User Date Valid To | Valid To Date of the Business User. | ### Additional Account Attributes The SAP S/4HANA Cloud connector supports aggregation of additional account attributes from the SCIM User API. These attributes are aggregated only when they are defined in the account schema. | Attribute Name | Type | Description | | --- | --- | --- | | Created | String | Account creation date of the Business User. Stored in `yyyy-MM-dd` format. | | Login Time | String | Last logon timestamp of the Business User. Stored in `yyyy-MM-dd+timestamp` format. | | User UUID | String | Global User ID of the Business User. | ## 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 S/4HANA Cloud 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 | | --- | --- | | Business Role ID | Business Role Unique Identifier. This is an Identity Attribute which must not be changed. | | Business Role Name | Business Role Name. | # Migrate VA-based Source to a SaaS Source > [!WARNING] > > - SaaS connector supports Direct Role Aggregation only. > - If your VA connector is using CSV-based role aggregation, switch to API -based (Direct) Role Aggregation before migrating. Some sources that are connected to virtual appliance (VA) clusters can be migrated to SaaS connections. This ensures data (users and entitlements) remain intact and can maintains your source configurations like access profiles, roles, password settings, and correlation configurations when switching from a VA cluster to a SaaS connection. To migrate a source from a VA-based source to a SaaS source, you will provide configuration details on a draft version of the source before publishing the source. > [!NOTE] > > - You must have an Admin or Source Admin user level to migrate a source. A draft version of the source is created. As your migration process is in progress the live source will continue to work as it is. For more information on the SAP S/4HANA Cloud SaaS connector, refer to the [SAP S/4HANA Cloud SaaS Supported Features](). ## Important Considerations Before Migrating - You do not need to edit additional configurations (other than connection credentials) to migrate the source. - If your source migration is in progress, please do not make any configuration changes to your live source as those can be overwritten once you apply the migration your draft version. - Once you've gone ahead with your migration, it can't be rolled back. Your source is permanently migrated to a SaaS source. - Any preview operations or configuration changes on the draft source will not impact the live source until you apply the migration. ## Migrating Sources To migrate your source, complete the following: 1. Go to **Admin \> Connections \> Sources**. 2. Select or edit the VA-based source you want to migrate. 3. Open the source configuration, and select **Migrate to SaaS**. 4. When prompted, select **Continue**. A draft version of the source is created. The live source will continue to work. 5. Select **Connection Settings**. 6. Re-enter encrypted configuration details. For example, you might need to re-enter the Client Secret, Password, Refresh Token, Personal Access Token (PAT), or Certificates to migrate from the VA cluster to the SaaS connection. > **Important** > > Avoid editing the other configuration options in the draft source. 7. Select **Review and Test**. 8. Select **Test Connection**. 9. (Optional) Select **Accounts**. If you successfully tested your connection in **Review and Test**, you can select **Preview** to display a subset of accounts from the application that will be mapped to SailPoint identities. This can help ensure you are accurately connecting identity data from the application with SailPoint identities. 10. (Optional) Select **Entitlements**. If you successfully tested your connection in **Review and Test** and your source type supports entitlement type configuration, you can select **Preview** to view a preview of entitlements using the current configuration settings. 11. When you've finished reviewing your changes and successfully tested your connection, select **Apply Migration**. Your changes will be applied to the live source and the draft source will be deleted. ## Viewing Source Migration Status You can view the status and creation date of draft sources. 1. Go to **Admin \> Connections \> Sources \> Source Migration Status**. 2. Select **Source Migration Status**. 3. To view or edit the draft source, select **Actions** ![]() **\> Preview** on the draft source. 4. To delete the draft source, select **Actions** ![]() **\> Delete** on the draft source. # Enable Connector Logging This topic provides the steps needed to enable logging on SailPoint using REST APIs. > [!NOTE] > > This topic only applies to VA-based integrations. > [!NOTE] > > The examples provided might not match your configuration. Use the logging levels and logging classes reference at the bottom of the topic to configure your API responses to match your connector. This process is broken up into four steps: 1. Identify the Virtual Appliance (VA) cluster on which you want to enable logging. 2. Get the logging configuration for the existing VA cluster. 3. Update the VA cluster to enable logging levels. 4. Observe logging changes to the logging levels. ### Identify the Virtual Appliance Cluster Select the VA on which you need to enable logging using REST API. If you already know the VA application's `id`, proceed to [Get the Logging Configuration](<#get-the-logging-configuration>). 1. Make the following call to the REST API to return a list of available VA clusters: GET /v3/managed-clusters The REST API returns a response that looks similar to the following: ```json [ { "id": "2c9180866166b5b0016167c32ef31a66", "name": "Development Cluster", "description": "Development Cluster", "clientType": "CCG", "ccgVersion": "373_535_70.2.0", "pinnedConfig": true, "logConfiguration": null }, { "id": "2c9180846a93ce60016ab29f039944de", "name": "Cloud Cluster", "description": "Cloud Cluster", "clientType": "CCG", "ccgVersion": "373_535_70.2.0", "pinnedConfig": true, "logConfiguration": { "clientId": null, "durationMinutes": 60, "expiration": "2020-12-15T19:13:36.079Z", "rootLevel": "DEBUG", "logLevels": { "sailpoint.connector.ADLDAPConnector": "DEBUG" } } } ] ``` > **Note** > > The previous example code shows two VA clusters. One VA cluster has a log configuration and the other does not (refer to the `logConfiguration` value in each returned VA cluster). This is because one of the clusters already has logging enabled. This is just an example configuration, and your environment may not have logging enabled on a cluster. 2. Identify the VA cluster that you want to enable logging on by its name or description and record its `id` attribute. ### Get the Logging Configuration Get your selected VA's cluster logging configuration and identify the values you need to update. 1. Make the following call to the REST API to return the VA cluster's logging configuration. Replace `{id}` with the VA cluster's `id` attribute value recorded earlier. GET /v3/managed-clusters/{id}/log-config - If the VA doesn't have a logging configuration currently set, it returns `204 No Content` as a response. - If the VA has an existing logging configuration, it returns something similar to the following: ```json { "clientId": null, "durationMinutes": 60, "expiration": "2020-12-15T19:13:36.079Z", "rootLevel": "DEBUG", "logLevels": { "sailpoint.connector.ADLDAPConnector": "DEBUG" } } ``` You'll need to configure the following information in the response: - `durationMinutes` is the number of minutes logging should remain enabled. - `rootLevel` is the default level for all logs. For more information, refer to [Logging Levels](<#logging-levels>). - `logLevels` is a map object with logging classes as keys and logging levels as values. - For keys, refer to [Logging Classes](<#logging-classes>) for commonly used logging classes. - For a list of available values, refer to [Logging Levels](<#logging-levels>). ### Update Logging Configuration Update the VA cluster configuration returned by the REST API to update the logging settings as needed. 1. Make the following call to the REST API to update the VA cluster's logging configuration. Replace `{id}` with the VA cluster's `id` attribute value recorded earlier. PUT /v3/managed-clusters/{id}/log-config 2. Submit your configuration changes to the REST API in a JSON body. - If the VA cluster did not already have a logging configuration and you received a `204 No Content` response, you can create a new one. - If the VA returned a configuration, you can edit it to include the changes. The JSON body should be as follows: ```json { "durationMinutes": 60, "rootLevel": "DEBUG", "logLevels": { "sailpoint.connector.ADLDAPConnector": "DEBUG" } } ``` Consider the following as you edit the JSON: - `durationMinutes` is the number of minutes logging should remain enabled. - `rootLevel` is the default level for all logs. For more information, refer to [Logging Levels](<#logging-levels>). - `logLevels` is a map object with logging classes as keys and logging levels as values. - For keys, refer to [Logging Classes](<#logging-classes>) for commonly used logging classes. - For a list of available values, refer to [Logging Levels](<#logging-levels>). If the update was successful, the REST API should return a response similar to the following: ```json { "clientId": null, "durationMinutes": 60, "expiration": "2020-12-15T19:13:36.079Z", "rootLevel": "DEBUG", "logLevels": { "sailpoint.connector.ADLDAPConnector": "DEBUG" } } ``` ### Observe Logging Changes Approximately five minutes after you update the configuration, the VA cluster starts generating log files you can review. You can view the log files in **ccg.log**. ### References The tables in this reference section list information that can be helpful when creating the JSON body you'll use to configure the VA cluster's configuration file. #### Logging Levels | Logging Level | Description | | --- | --- | | ERROR | Designates error events that might still allow the connector to continue. | | WARN | Designates potentially harmful situations. | | INFO | Designates information messages that highlight process at a coarse-grain level. | | DEBUG | Very verbose. Fine grain logging levels used for development and debugging. | | TRACE | Most verbose. Finer grain logging levels than debugging. | #### Logging Classes | Connector | Logging Class | | --- | --- | | Active Directory | sailpoint.connector.ADLDAPConnector sailpoint.connector.LDAPConnector | | AIX | openconnector.connector.unix.AIXConnector openconnector.connector.unix.UnixConnector | | Amazon Web Services | logger.aws.name=openconnector.connector.aws logger.aws.level=trace logger.aws.additivity = false logger.aws.appenderRef.rolling.ref = STDOUT | | Atlassian Suite Cloud | sailpoint.connector.OpenConnectorAdapter openconnector.connector.atlassian.AtlassianConnector | | Atlassian Data Center | sailpoint.connector.OpenConnectorAdapter openconnector.connector.atlassian.AtlassianDataCenterConnector | | Microsoft Entra ID | sailpoint.connector.AzureADConnector | | Box | openconnector.connector.BoxNetConnector sailpoint.connector.OpenConnectorAdapter | | Cerner | openconnector.connector.CernerConnector sailpoint.connector.OpenConnectorAdapter | | Delimited File | logger.DelimitedFileConnector.name = sailpoint.connector.DelimitedFileConnector logger.DelimitedFileConnector.level = debug logger.DelimitedFileConnector.additivity = false logger.DelimitedFileConnector.appenderRef.rolling.ref = STDOUT | | Dropbox | openconnector.connector.DropBoxConnector sailpoint.connector.OpenConnectorAdapter | | Epic | openconnector.connector.EPICConnector sailpoint.connector.OpenConnectorAdapter | | GE Centricity | openconnector.connector.GECentricity sailpoint.connector.OpenConnectorAdapter | | Google Apps / G Suite | openconnector.connector.GoogleAppsDirect sailpoint.connector.OpenConnectorAdapter | | IBM i | openconnector.connector.IBMiConnector | | Lotus Domino | sailpoint.connector.LotusDomino | | JDBC | sailpoint.connector.JDBCConnector | | Sun One LDAP | sailpoint.connector.LDAPConnector | | Linux | openconnector.connector.unix.LinuxConnector sailpoint.connector.OpenConnectorAdapter sailpoint.connector.UnixConnector | | Microsoft Office365 | sailpoint.connector.Office365Connector | | Microsoft SQL Server | sailpoint.connector.mssql.serviceimpl.MSSQLServerConnectorV2 | | Okta | logger.openconnector.name = openconnector.connector.okta.OktaConnector logger.openconnector.level = debug logger.openconnector.additivity = false logger.openconnector.appenderRef.rolling.ref = STDOUT | | Oracle Database | sailpoint.connector.OracleDBConnector sailpoint.connector.JDBCConnector | | Oracle E-Business | sailpoint.connector.OracleEBSConnector sailpoint.connector.JDBCConnector | | Oracle Fusion HCM | openconnector.connector.oraclefusionhcm.OracleFusionHCMConnector sailpoint.connector.OpenConnectorAdapter | | Oracle HCM Cloud | sailpoint.connector.oraclehcmcloud.OracleHCMCloudConnector | | Oracle HRMS | sailpoint.connector.OracleAppsHRMSConnector sailpoint.connector.JDBCConnector | | Oracle Netsuite | openconnector.connector.netsuite.NetsuiteConnector | | PeopleSoft ERP | openconnector.connector.PeopleSoftConnector sailpoint.connector.OpenConnectorAdapter | | PeopleSoft HRMS | sailpoint.connector.PeopleSoftHRMSConnector | | RemedyForce | sailpoint.connector.ForceConnector | | RSA Authentication Manager | openconnector.connector.RSAConnector openconnector.connector.rsa.RSAHTTPClient sailpoint.connector.OpenConnectorAdapter | | Salesforce | sailpoint.connector.ForceConnector | | SAP Concur | openconnector.connector.sapconcur.SAPConcurConnector | | SAP - Direct | sailpoint.connector.SAPConnector sailpoint.connector.SAPInternalConnector | | SAP GRC | logger.SAPGRCConnector.name = sailpoint.connector.sapgrc logger.SAPGRCConnector.level = debug logger.SAPGRCConnector.additivity = false logger.SAPGRCConnector.appenderRef.rolling.ref = STDOUT | | SAP HR/HCM | sailpoint.connector.SAPHRInternalConnector | | SCIM 1.1 | openconnector.connector.SCIMConnector sailpoint.connector.OpenConnectorAdapter | | SCIM 2.0 | openconnector.connector.scim2.SCIM2Connector sailpoint.connector.OpenConnectorAdapter | | ServiceNow | openconnector.connector.servicenow.ServiceNowConnector openconnector.connector.servicenow.ServiceNowRestClient sailpoint.connector.OpenConnectorAdapter | | ServiceNow Service Desk Integration | openconnector.connector.servicedesk.ServiceNowServiceDeskConnector sailpoint.connector.OpenConnectorAdapter | | Siebel | openconnector.connector.SiebelConnector sailpoint.connector.OpenConnectorAdapter | | Snowflake | openconnector.connector.snowflake.SnowflakeConnector sailpoint.connector.OpenConnectorAdapter | | Solaris | openconnector.connector.unix.SolarisConnector openconnector.connector.unix.UnixConnector sailpoint.connector.OpenConnectorAdapter | | SuccessFactors | sailpoint.connector.SuccessFactorsConnector | | Sybase | sailpoint.connector.SybaseDirectConnector sailpoint.connector.JDBCConnector | | Webex | openconnector.connector.Webex sailpoint.connector.OpenConnectorAdapter | | Workday | openconnector.connector.WorkDay sailpoint.connector.OpenConnectorAdapter | | Workday Accounts | openconnector.connector.workdayaccounts openconnector.connector.workdayaccounts.WorkdayAccountsConnector sailpoint.connector.OpenConnectorAdapter | | Web Services | sailpoint.connector.WebServices | | XML | openconnector.connector.XMLConnector sailpoint.connector.OpenConnectorAdapter | | Yammer | openconnector.connector.YammerConnector sailpoint.connector.OpenConnectorAdapter | | Zoom | openconnector.connector.zoom.ZoomConnector sailpoint.connector.OpenConnectorAdapter | # 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]() ## Invalid File Extension If an incorrect **Role Details File Name** is provided without the extension of the file, the following error message appears during aggregation: ```text "Exception during aggregation of Object Type account on Application SAP HANA. Reason: Unable to create iterator sailpoint.connector.InvalidConfigurationException: [InvalidConfigurationException] [Possible suggestions] Ensure that Role Details File Path is correct and accessible. [Error details] Invalid Role Details file path." ``` **Resolution**: Ensure that the .csv file extension is provided. ## Incorrect Connection Credentials The following error message appears when incorrect inputs are provided for the **API URL**, **User name** or **Password**: ```text For Invalid URL 403 Not Authorized. ``` ```text For Invalid UserName / Password 401 Not Authorized. ``` **Resolution**: Ensure that the inputs provided for the **API URL**, **User name** and **Password** are correct and valid. ## Test Connection Fails with an Error Message ```text [ConnectorException] [Possible suggestions] Provide correct configurations, ensure user is active with correct set of permissions and credentials. [Error details] Error extracting response from XML ``` **Resolution**: Ensure the value of the **URL** is entered correctly. Refer to [SAP S/4HANA Cloud Prerequisites]() for more information. ## CSV Count Does Not Match The number of roles in the CSV file (X) does not match the number of roles in SCIM (Y). ```text Exception during aggregation of Object Type Group on Application SAPS4HANACloudApp. Reason: sailpoint.connector.ConnectorException: [ ConnectorException ] [ Possible suggestions ] Provide correct configurations, ensure user is active with correct set of permissions and credentials. [ Error details ] [ InvalidConfigurationException ] [ Possible suggestions ] Please correct CSV file to match the CSV roles and direct aggregation roles. ``` Example - Current CSV count: 133, SCIM count: 134 \[ Error details \] Mismatch in the number of CSV roles and direct aggregation roles using SCIM API. **Resolution**: Ensure that the latest role CSV file is uploaded and that the role count in the CSV file matches the number of roles in S/4HANA Public Cloud. ## Create User Option Is Not Checked, and the User Trying to Create an Account ```text sailpoint.connector.ConnectorException: To create a business user, please enable 'create business user account' checkbox ``` **Resolution**: Ensure that the **Create Business User** checkbox is enabled in the configuration parameters. ## Create User Account Is Failing with an Error When the Worker ID API Is Used ```text sailpoint.connector.ConnectorException: java.lang.Exception: Worker Id Api execution failed with error : java.lang.Exception: Could not find worker ID ``` **Resolution**: Ensure that the worker has valid work agreements assigned in the S/4HANA Cloud system. ## Incorrect Access Sunset Timing for SAP HANADB Users Due to Time Zone Differences When a role is sunset for SAP HANADB users, the actual expiration time may be incorrect. It might not match the requester's expectations due to how different time zones are processed. **Resolution**: The sunset end date will now respect the requester's local time zone (matching their computer's system time) instead of relying on a fixed server time zone. Examples: ```text Someone in EST picks end date 10 June → access ends at 12:00 AM on 10 June EST. ``` ```text Someone in IST picks the same date 10 June → access ends at 12:00 AM on 10 June IST. ``` ## Account Aggregation Fails Due to SCIM Groups API Timeout Account aggregation fails due to SCIM Groups API timeout issues. **Resolution**: 1. Add `groupPageSize` in the connector configuration and set the value to 500. 2. If the issue persists, increase `connTimeout` to 5 minutes. # Timeout Errors and Settings Timeout errors might occur when SailPoint is waiting for a response from the Virtual Appliance (VA). These errors are applicable to all connectors and tend to occur during the setup of sources or when sources are down. This document is designed to give specific information that can be used to resolve these errors. Each timeout attribute has a default time value that is listed in seconds or minutes. Increasing the time value may resolve the error as it will allow for longer communication time between the two systems, thus avoiding the timeout error. > [!IMPORTANT] > > Add the necessary attributes or values before performing the "replace" operation, as missing attributes will cause the operation to fail. To increase the communication time, increase the value of the appropriate timeout attribute. Then submit the change to the VA using the SailPoint REST API. > [!NOTE] > > For more information on SailPoint's REST APIs, refer to [Best Practices: REST API Authentication]() and [REST API - Update Source (Partial)]() in the SailPoint Developer Community. ### aggregateTimeout **Description:** This parameter is set for the aggregation timeout, measured in seconds. **Resolution:** Increase the `aggregateTimeout` value gradually to optimize aggregation. Start with 180, then increase to 600, 900, and finally 1800. The maximum value is 3600 seconds. For example: If your current time value is 180 seconds, update the `aggregateTimeout` attribute as follows: ```json [ { "op": "replace", "path": "/connectorAttributes/aggregateTimeout", "value": 600 } ] ``` ### healthCheckTimeout **Description:** This parameter is set for the test connection and health check timeout. **Resolution:** The default value is 30 seconds. If the timeout error continues, increase the value in 15 second increments and try again. For example: If your current time value is 30 seconds, update the `healthCheckTimeout` attribute as follows: ```json [ { "op": "replace", "path": "/connectorAttributes/healthCheckTimeout", "value": 45 } ] ``` ### provisioningTimeout **Description:** This parameter is set for provisioning timeout. **Resolution:** Increase the `provisioningTimeout` value gradually to optimize provisioning. Start with 180, then increase to 360, and finally 600. The maximum value is 600 seconds. For example: If your current time value is 180 seconds, update the `provisioningTimeout` attribute as follows: ```json [ { "op": "replace", "path": "/connectorAttributes/provisioningTimeout", "value": 360 } ] ``` ### timeout **Description:** This parameter is set for pass-through authentication timeout. **Resolution:** The default value is 15 seconds. If the timeout error continues, increase this value in 15 second increments and try again. For example: If your current time value is 15 seconds, update the `timeout` attribute as follows: ```json [ { "op": "replace", "path": "/connectorAttributes/timeout", "value": 30 } ] ``` ### apiTimeout **Description:** This parameter is set for API time tracking; customers can check it using an external tool. **Resolution:** The default value is 60 seconds. If the error continues, increase the value by 15 second increments and try again. For example: If your current time value is 60 seconds, update the `apiTimeout` attribute as follows: ```json [ { "op": "replace", "path": "/connectorAttributes/apiTimeout", "value": "75" } ] ``` ### timeoutInSeconds **Description:** This parameter helps prevent the VA from waiting indefinitely for an API response, ensuring efficient handling of API requests. For example: If your current time value is 30 seconds, update the `timeoutInSeconds` attribute as follows: ```json [ { "op": "replace", "path": "/connectorAttributes/timeoutInSeconds", "value": "15" } ] ```