# SailPoint SAP Analytics Cloud SaaS Connector Documentation > SAP Analytics Cloud SaaS Connector Documentation # Documentation # Configuring the Leaver Process The leaver process can be configured in the following way: ## Remove all entitlements using LifeCycleState All entitlements assigned to a SAP Analytics Cloud account can be removed when the identity to which this account is correlated to reaches the end of its LifeCycle. 1. Create a Group (Team) in SAP Analytics Cloud that has all disabled users as its members. 2. Configure a LifeCycleState for the leaver Identities, and assign the Group for disabled users to this LifecycleState. For more information, refer to [Setting Up Lifecycle States - SailPoint Identity Services](). 3. When an Identity enters this LifeCycleState, all roles and groups assigned to a SAP Analytics Cloud account will be removed and the account will become a member of the group that was assigned to the leaver LifeCycleState. 4. Admins should manually disable all members in this Group from the SAP Analytics Cloud UI. Admins can be notified via email when an identity enters the leaver LifeCycleState. For more information, refer to [Setting Up Lifecycle States - SailPoint Identity Services](). # Connecting SailPoint and SAP Analytics Cloud SaaS To connect SailPoint with SAP Analytics 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 Analytics Cloud SaaS. > [!NOTE] > > **Screenshot** > > [![Connection Settings]()]() 1. Enter the host URL of the SAP Cloud Identity Services Tenant as the **Base URL**. 2. Enter the ID of SAP IPS Proxy system created for SAP Analytics Cloud as the **System ID**. You will get the system ID from the URL. For example, `https:///admin/#/proxySystems//` 3. Enter the SAP IPS technical user credentials (as mentioned in [Prerequisites]()) in **Client ID** and **Client Secret**. 4. Save the connection configuration. ## Aggregation Settings > [!NOTE] > > **Screenshot** > > [![Aggregation Settings]()]() 1. Enter the **Page Size** as the number of records to fetch in one request. The default is 100. Supported values are 10 to 100. 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. # Frequently Asked Questions The following are Frequently Asked Questions (FAQs) for this connector. ## What happens to private content of a user when their account is deleted? **Answer**: If you choose the delete option for the leaver/termination process, you will lose the private content owned by deleted users. This is due to a bug in the SAP API. # Integrating SailPoint with SAP Analytics 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. SAP Analytics Cloud is an end-to-end cloud solution that brings together business intelligence, augmented analytics, predictive analytics, and enterprise planning in a single system. SAP Analytics Cloud Identity Governance is a new SailPoint SAP Cloud integration that empowers businesses to enhance the security and compliance of their systems and data. It offers robust tools for efficiently managing and overseeing user access, roles, and entitlements ensuring high control and governance. > [!NOTE] > > This integration of SAP Analytics Cloud has been built using SAP Identity Provisioning Services (IPS). The credentials used to connect to SAP Analytics 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 Analytics Cloud SaaS connector supports the following features: - Aggregation - Account Aggregation - Groups Aggregation - Roles Aggregation > **Note** > > SailPoint does not support direct role aggregation. Roles are aggregated as promoted attributes. - Add / Remove Entitlement - Groups - Roles - Account Provisioning - Create, Update (in the update operation, only the Manager ID is supported) - Delete. For more information, refer to [FAQs](). - Enable and Disable ### 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]()]() > > [![Privilege Level - Low]()]() ## Supported Managed Systems - SAP Analytics Cloud standard edition. ## Prerequisites - The following set of credentials must be created to configure the IPS Proxy of SAP Analytics Cloud 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. The configuration steps are detailed in the following links: ### Configure OAuth Client for SAP Analytics Cloud Configure the SAP Analytics Cloud (SAC) OAuth client by performing the following steps: - Prerequisites - You must have the necessary permissions to create the OAuth client. - Sign in to the SAC System and go to **OAuth Client Management**. From the side navigation menu, go to **System \> Administration \> App Integration** tab. - Under **Configured Clients**, select **Add a New OAuth Client**. In the dialog, provide the following details: - **Name**: Provide a name for the OAuth client. For example, `My SAP S/4HANA tenant`. - **OAuth Client ID**: Specify an ID for the OAuth client. For example, `my300xxx`. - Select the purpose as **Interactive Usage and API Access**. In **Access**, select **User Provisioning** to allow third-party applications to access SAC public APIs without a SAML assertion. - Select **Save**. ### Configure Technical User in SAP Identity Provisioning Service Perform the following steps to configure the technical user and connect to identity provisioning. #### Enable Basic Authentication 1. Sign in to the SAP Cloud Identity Services admin console, and go to **Users & Authorizations \> Administrators**. 2. Add an administrator user of the type `System`, and then provide the name of the user. 3. Select the **Access Proxy System API** permission in **Configure Authorizations**. 4. Select **Save**. 5. 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 to SAP Analytics Cloud. ### Configure the SAP Identity Provisioning Service Proxy System Use one of the following options to configure the proxy system. It is recommended to use 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. > 3. Select **Import File**, and browse to the downloaded file. > [!NOTE] > > **Option 2 - Use the manual process** > > 1. Sign in to the SAP Cloud Identity Services admin console. Go to **Identity Provisioning \> Proxy Settings**, and select the **\+Add** button. > 2. Enter the following values on the configuration details page. > > - Type: `SAP Analytics Cloud` > - System Name: `User defined name` > - Description: `User defined description` > 3. Select **Save**. > 4. Set the read transform to exchange data with the target system in the SCIM2 compliant format. > > [![Read Transform]()]() > > 1. Select **Read Transformation**, and switch to the JSON editor. > 2. Select **Edit link**, and replace the transformation content with the provided [data](). > 3. Select **Save**. > 5. Set the write transform to exchange data with the target system in the SCIM2 compliant format. > > [![Write Transform]()]() > > 1. Select **Write Transformation**, and switch to the JSON editor. > 2. Select **Edit link**, and replace the transformation content with the provided [data](). > 3. Select **Save**. > 6. Select **Properties**. It is mandatory to set properties to configure the proxy connection to target systems. > > [![Properties]()]() > 7. The following table contains the properties for the SAP Analytics Cloud system. Enter the values, and then select **Save**. > > | Property Name | Description and Value | > | --- | --- | > | Type | Enter `HTTP` | > | URL | Enter the `URL` to your SAP Analytics Cloud system without adding the path information | > | ProxyType | Enter `Internet` | > | Authentication | Enter `BasicAuthentication` | > | User | Enter the `Client ID` to retrieve the OAuth access token for SAP Analytics Cloud | > | Password | Enter the `Client Secret` to retrieve the OAuth access token for SAP Analytics Cloud. | > | OAuth2TokenServiceURL | Enter the `URL` of the access token provider service for your SAP Analytics Cloud instance. This token URL is listed in the OAuth Clients section of the App Integration page. For more information, refer to [Authorize API Access for OAuth Clients](). | > | scim.api.csrf.protection | Specifies whether to fetch a Cross-Site Request Forgery (CSRF) token when sending requests to the system. This property is automatically added to the system. Default value: `enabled`. | > | csrf.token.path | The path that is appended to the URL to retrieve the CSRF token. This property is automatically added in the system. Value: `/api/v1/scim2/Users?count=1` | > | sac.api.version | Manages the version of SAP Analytics Cloud SCIM API. Value: Indicates that SAP Analytics Cloud SCIM API version 2 is used. | > | (Optional) ips.trace.failed.entity.content | If a provisioning job repeatedly fails and you need problem investigation, you can enable logging and tracing for the personal and sensitive data of your provisioned entities. To do this, set the property to `true`. | ## Required Permissions The following permissions are required for the OAuth client and Technical user (IPS): - SAP Analytics Cloud (to configure the OAuth Client) - OAuth client required to be created by System user. Select **Interactive Usage and API Access**. In **Access** select **User Provisioning** to allow third-party applications to access SAC public APIs without an SAML assertion. - SAP Identity Provisioning Service (to configure technical user) - Technical user required to be created by Tenant Administrator. Select **Access Proxy System API** permission in **Configure Authorizations**. # Machine Account Attributes ## Machine Account Provisioning Attributes Machine account creation uses the same source attributes as standard account creation. Refer to [Provisioning]() for the complete list of supported attributes and their descriptions. Refer to [Machine Identity Security Overview]() for more information. # Provisioning The SAP Analytics Cloud SaaS connector supports provisioning, allowing you to create and manage accounts and entitlements in SAP Analytics 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] > > The attributes marked with an asterisk (\*) are required attributes. | Account Attribute | Description | | --- | --- | | User Name \* | The user's 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 Email ID. | | Manager ID | The user's primary supervisor's ID. | # 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 Analytics 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 Analytics Cloud SaaS source, the default correlation mapping is: | Account Attribute | Operation | Identity Attribute | | --- | --- | --- | | 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 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 | ### Default Account Attributes The SAP Analytics Cloud SaaS connector supports the following default account schema attributes and customer configurable attributes. The attributes must be defined as strings if not specified. > [!NOTE] > > For support of additional attributes, refer to the [FAQs](). | Attribute Name | Description | | --- | --- | | User Name | The user's login name. | | ID | A unique identifier for the user. | | Active | The user's active status. | | First Name | The user's first name. | | Last Name | The user's last name. | | Display Name | The user's display name. | | Email | The user's work email address. | | Manager ID | The user's primary supervisor ID. | | Roles | The user's Role assignments. | | External Id | An identifier for the resource as defined by the provisioning client. | | Groups | Groups linked to the user through role assignments. | | Resource Location (Only aggregation) | Resource Location | | Email Value (Only aggregation) | Email addresses associated with the user in string format | | Email Type | Email type (work, home, etc.) | | Primary Email | Indicates whether the email address is the primary email | | Role Display Name | Display name of assigned roles | | Manager Reference | Reference URI for the manager | | Is Concurrent User | Indicates whether the user is concurrent | | Data Access Language | User data access language | | Number Formatting | User number formatting preference | | Date Formatting | User date formatting preference | | Time Formatting | User time formatting preference | | IDP User ID | Identity provider user identifier | | Marketing Email Opt-In | Indicates marketing email opt-in status | | System Notifications Email Opt-In | Indicates system notification email opt-in status | | Cleanup Notifications Days | Number of days for cleanup notifications | ## 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 Analytics 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 | | --- | --- | | ID | A unique identifier for the group. | | Group Name | The name of the group. | | Roles | The roles associated with that group. | | Members | The members of the group. | | Description | The group's description. | ### Default Role Attributes The SAP Analytics Cloud 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 | | --- | --- | | Role Value | The role's value. | # 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](). ## Irreparable error,"status":500 when processing entities **Issue**: The connector cannot process more entities due to irreparable error","status":500. This can happen if there is a space in the property file attribute. **Resolution**: Go to **IPS Proxy \> Properties User Attribute** and ensure there are no spaces in between the property file attributes. ## Property has invalid syntax!","status":400 when initializing SacDelegatingReadConnector **Issue**: A space is in the URL field causing the following error: connector.common.http.exception.HttpException: {"schemas":\["urn:ietf:params:scim:api:messages:2.0:Error"\],"detail":"Can not initialize SacDelegatingReadConnector: com.sap.cloud.ips.connectors.api.ConnectorSetupException: Property has invalid syntax!","status":400} **Resolution**: Ensure there are no spaces in the URL. ## Java.lang.IllegalArgumentException OAuth error **Issue**: A mandatory parameter is missing in properties causing the error java.lang.IllegalArgumentException: OAuth client configuration is invalid! **Resolution**: Ensure all the required parameters are entered in the properties. ## Execution Fails on Behalf of a Tenant Due to Missing Authentication **Issue**: This error displays when authentication is missing in properties. **Resolution**: Enter the Authentication type. ## Request is unparsable, syntactically incorrect, or violates schema **Issue**: This error can happen if you update an id that was recently added and the email address has not yet been used to sign in to the system. **Resolution**: Ensure it is a valid user that has logged in with their email. ## ConnectorException during Update Account or Create Account operations with large groups **Issue**: The connector fails with ConnectorException errors during Update Account or Create Account operations when provisioning users to groups with a large number of members (100 or more). The following errors might appear: - `java.net.SocketTimeoutException: Read timed out` during Update Account operations - HTTP 409 Conflict with `scimType: uniqueness` and a detail message indicating the specified version number does not match the resource's latest version number during Create Account operations **Resolution**: Follow these steps in order. For the SAP Analytics Cloud connector, all parameters must be prefixed with `ips0_`. 1. Add the following entry to the source XML using the REST APIs to increase the connection timeout. The value is in minutes. ```json [ { "op": "add", "path": "/connectorAttributes/ips0_customTimeout", "value": "5" } ] ``` Test the provisioning operation again. If the issue is resolved, no further changes are needed. 2. If the issue persists, add the following entries to the source XML using the REST APIs one at a time. Test the provisioning operation after adding each entry. a. Enable updating groups via users: ```json [ { "op": "add", "path": "/connectorAttributes/ips0_updateGroupsViaUsers", "value": "true" } ] ``` b. Enable PATCH operations for accounts: ```json [ { "op": "add", "path": "/connectorAttributes/ips0_usePatch", "value": "true" } ] ``` c. Enable PATCH operations for groups: ```json [ { "op": "add", "path": "/connectorAttributes/ips0_useGroupPatch", "value": "true" } ] ``` > [!IMPORTANT] > > The `ips0_` prefix is mandatory for this connector type. Without it, the keys do not take effect. > > Using PATCH operations instead of PUT resolves timeout issues for large user groups. PUT operations send the entire group membership payload, which can cause timeouts from SAP IPS. > > SAP IPS might return HTTP 429 (Too Many Requests) for large provisioning operations. This is a known SAP-side rate limiting issue. Contact SAP support for assistance. > [!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.