# SailPoint SAP Concur SaaS Connector Documentation > SAP Concur SaaS Connector Documentation # Documentation # Connecting SailPoint and SAP Concur SaaS To connect SailPoint with SAP Concur, 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 Concur SaaS. > [!NOTE] > > **Screenshot** > > [![alt text]()]() 1. Select **Connection Settings** from the menu. 2. Enter the **Host URL**. This is the SAP Concur base URL that relates to the client location, government regulations, and other special requirements. The table below lists the URLs for different regions. > **URL Table** > > | Data Center | Base URL | > | --- | --- | > | US | [https://us.api.concursolutions.com]() | > | US2 | [https://us2.api.concursolutions.com]() | > | EMEA | [https://emea.api.concursolutions.com]() | > | EU | [https://eu.api.concursolutions.com]() | > | EU2 | [https://eu2.api.concursolutions.com]() | > | China\* | [https://cn.api.concurcdc.cn]()
\*Access may be forbidden by SAP to this API in the china region. If issues arise, contact SAP support. | > | PSCC | [https://usg.api.concursolutions.com]() | 3. The **Grant Type** is Refresh Token (preselected). 4. Enter the **Company ID**, **Client ID** and **Client Secret** for Oauth 2.0 authentication. 5. Enter the **Refresh Token** used to generate an access token. 6. Select **Save**. ## Aggregation Settings > [!NOTE] > > **Screenshot** > > [![alt text]()]() 1. Select **Aggregation Settings** from the menu. 2. Enable **Include Inactive Users** if you wish to include inactive users in the account aggregation. 3. Enter the **Page Size** as the number of records to fetch in one request. Default = 50; Maximum value =100 4. 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. # Aggregation of Custom Roles To aggregate the custom roles, add the following entry keys in the Source XML using [SailPoint Update Source Partial REST API](). The values provided should be as per the roles you want to aggregate. ```javascript [ { "op": "add", "path": "/connectorAttributes/additionalRolesList", "value": [ { "Description": "First Role", "Group Aware": false, "Product Area": "Y", "Role Code": "001", "Role Name": "First" } ] } ] ``` # Integrating SailPoint with SAP Concur 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 Concur Cloud integration with SailPoint connector provides Identity Governance on Expense management services provided by Concur. The integration supports enforcing policies and permissions for granting and revoking access to systems and data based on user identities, roles, and associated groups for Expense. > [!NOTE] > > To view the latest features, enhancements, and fixes for all SaaS connectors, refer to the [SaaS Release Notes]() page. ## Supported Features The SAP Concur SaaS connector supports the following features: > [!IMPORTANT] > > Before you can use any of the following items marked with an asterisk (\*), SailPoint must activate the feature for your site. - Aggregation - Account Aggregation - Groups Aggregation - Add/Remove Entitlement - Groups - Account Provisioning - Create User - Update User (Attributes) - Enable/Disable User For more information on features, refer to [Source Features](). ## Privilege Classification SailPoint Privilege Classification helps organizations systematically categorize and manage the privilege levels of entitlements within their sources. By classifying entitlements as high, medium, or low, administrators can better understand the potential risk and impact associated with specific access rights. This allows automatic assignment of privilege levels based on system recommendations, custom-defined criteria, or a same level across all entitlements. | Privilege Level | Description | | --- | --- | | High | Administrative level access to accounts | | Medium | Administrative level access for a specific role or function | | Low | Only basic access of data | > [!NOTE] > > To manage Privilege Classification, users must have administrative roles such as Org Admin, Source Admin or Source Sub-Admin. For more information, refer to [Managing Privilege Classification](). > [!NOTE] > > **Example** > > [![Recommended Privilege Level - High]()]() > > [![Recommended Privilege Level - Medium]()]() > > [![Recommended Privilege Level - Low]()]() ## Supported Managed Systems - Concur Expense Professional Edition ## Prerequisites - You must set up a Client Application to establish Concur integration with SailPoint and perform all the operations. > [!NOTE] > > The client application uses the refresh\_grant to request a new access token as the initial step of accessing protected resources of SAP Concur services. ### Create New Application and Generate the Company Request Token 1. Sign in to [Concur]() and go to **Administration \> Company \> Authentication Admin**. 2. Select **OAuth 2.0 Application Management \> Create New App**. 3. Verify that the necessary permissions (called "scopes") are in place. For more information on assigning scopes, refer to [Required Permissions](<#required-permissions>). 4. Return to the **Authentication Administration** page and select **Company Request Token**. 5. Enter the Client ID in the **App ID** field and select **Submit**. 6. Upon submission, you will receive the **Company UUID** and the **Company Request Token**. > [!NOTE] > > The request token has a lifespan of 24 hours. It must be exchanged for a refresh token and access token by the application owner before it expires. ### Obtain a Refresh Token 1. Use the generated **Company Request Token** as a password. 2. Replace the following values and run the Password Grant CURL command to obtain an Access Token and Refresh Token. ```bash curl -X POST 'https://eu2.api.concursolutions.com/oauth2/v0/token' \ -H 'Content-Type: application/x-www-form-urlencoded' \ --data-urlencode 'client_id=' \ --data-urlencode 'client_secret=' \ --data-urlencode 'grant_type=password' \ --data-urlencode 'username=' \ --data-urlencode 'password=' \ --data-urlencode 'credtype=authtoken' ``` > [!NOTE] > > If the refresh token is not used after a certain period of time, it may expire. If this happens, the authorization process will need to be reinitiated in the client application. ## Required Permissions Provide the below scopes in **Concur \> App Details** as per your requirement. > [!NOTE] > > **Screenshot** > > [![alt text]()]() The allowed Grants are: **refresh\_token** and Password | Operation | Scopes | | --- | --- | | Aggregation | identity.user.ids.read, identity.company.core.read, user.provision.read, identity.user.core.read, identity.user.coresensitive.read, identity.user.enterprise.read, spend.user.general.read, openid | | Provisioning | identity.company.core.writeonly, user.provision.write, identity.user.coreenterprise.writeonly, identity.user.externalID.writeonly, spend.user.general.writeonly | # Machine Account Attributes ## Machine Account Provisioning 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. # Provisioning The SAP Concur SaaS connector supports provisioning, allowing you to create and manage accounts and entitlements in SAP Concur directly from SailPoint. **Prerequisite:** Your system is configured for provisioning. When SailPoint provisions new accounts to the source, it uses the attributes on the **Create Account** page as instructions or a template for what to include in the account. This page is also referred to as the *provisioning policy*. When new access is granted on a source where a user does not already have an account, SailPoint automatically includes account creation in the provisioning. This applies whether provisioning is started from an access request or from an automated role or lifecycle state assignment. For direct-connect sources, SailPoint automatically creates the account from this configuration. If the source is not configured as a direct-connect source, SailPoint creates and assigns a provisioning task to the source owner and includes the values for the source owner to use in manually creating the account. > [!IMPORTANT] > > This section describes the default **Create Account** configuration. SailPoint recommends that you work with Services to define a provisioning configuration specific to your company's needs. Be sure to verify large changes to the provisioning policy before implementation. Failure to do so might cause provisioning to fail. ## Default Create Account Attributes | Account Attribute | Description | | --- | --- | | Login Name | The name that can be used to sign in to Concur. | | First Name | The given or first name of the user. | | Last Name | The family or last name of the user. | | Email Address | The work email address for the user. | | Employee ID | The user's Employee Number. This is a required attribute to create an Expense User. | | Country/Region of Residence | The valid ISO 3166 country code. This is a required attribute to create an Expense User. | | Reimbursement Currency | The valid three digit currency code in the list of system reimbursement currencies. This is a required attribute to create an Expense User. | | Default Language | The valid locale from the list of configured locales as defined in `[RFC5646]`. For example, en-US. This is a required attribute to create an Expense User. | # 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 Concur 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 Concur SaaS source, the default correlation mapping is: | Account Attribute | Operation | Identity Attribute | | --- | --- | --- | | userName | Equals | Name | | id | Equals | Employee Number | | id | Equals | Name | | 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 Concur SaaS connector supports the following default account schema attributes and customer configurable attributes. The attributes must be defined as strings if not specified. > [!NOTE] > > The asterisk (\*) indicates 'Work' related attributes. | Attribute Name | Description | | --- | --- | | Manager ID | The user's Manager ID (aggregation only). | | ID | The user's unique identifier. This must not be changed. | | Login Name | The user's unique username. | | Active | The user's active status. | | First Name | The user's first name. | | Last Name | The user's last name. | | Display Name | The user's display name. | | Formatted Name | The user's formatted name. | | Title | The user's title. | | Email\* | The user's work Email address. | | Country\* | The user's country, expressed as a two-letter country code. | | Postal Code\* | The user's zip or postal code. | | Region\* | The user's state or region. | | Street Address\* | The user's street name. | | Phone Number\* | The user's primary phone number. | | Timezone | The user's Timezone. | | Start Date | The user's start date. | | Termination Date | The user's termination date. | | Employee ID | The user's employee number. | | Job Title | The user's job title. | | Cost Center | The user's cost center. | | Role Name | The user's role assignments. | | Entitlements | The user's entitlements or modules assignments. | | Groups | Groups linked to the user through role assignments. | | Reimbursement Currency | The user's reimbursement currency. | | Country/Region of Residence | The three-digit country code in the system list. | | Default Language | The locale from the list of configured locales as defined in `[RFC5646]`. For example, en-US. | | Reimbursement Type | The user's reimbursement type. | | Ledger | The user's ledger. | | Cash Advance Account Code | The user's cash advance account code. | | Is Test User | Indicates if the user is a test user. | | BI Manager | The user's Business Intelligence manager.
**Note**: The platform supports correlation of only one manager to the identity. To promote both BI Manager and Manager fields to identity, one manager field should be correlated using the manager correlation and the other will have to be promoted using an Identity Attribute Rule. | Other than the listed out-of-the-box attributes, the connector also supports some custom attributes. To configure custom attributes, refer to [Enable Custom Account Attribute Support](<#enable-custom-account-attribute-support>). ### Enable Custom Account Attribute Support Follow these steps to enable support for Custom Account Attributes: 1. Add the `supportCustomAttrs` attribute in the source using REST API and set it to true. For more information, refer to [Getting Started | SailPoint Developer Community](). Example: ```javascript { "supportCustomAttrs": "true" } ``` 2. Create a new map in the Concur source (connector attributes) named `jsonPathMapping` using REST APIs. 3. Create an entry in `jsonPathMapping` of the attribute for which support is to be enabled. Example to enable support for the `Custom17` field (similarly, all required custom 1-21 fields can be added): ```javascript { "customData.custom17": "['urn:ietf:params:scim:schemas:extension:spend:2.0:User'].customData[*][?(@.id=='custom17')].value" } ``` Example to enable support for the `OrgUnit1` field (similarly all required OrgUnit 1-6 fields can be added): ```javascript { "customData.orgUnit1": "['urn:ietf:params:scim:schemas:extension:spend:2.0:User'].customData[*][?(@.id=='orgunit1')].value" } ``` Entry to enable support for the Default expense report approver: ```javascript { "report.approver": "['urn:ietf:params:scim:schemas:extension:spend:2.0:Approver'].report[*].approver.value" } ``` Example entry to enable support for ADP Payroll Company Code fields (similarly all ADP payroll fields can be added): ```javascript { "adp.companyCode": "['urn:ietf:params:scim:schemas:extension:enterprise:2.0:Payroll'].adp.companyCode" } ``` 4. Add the custom attribute for which support is to be enabled in Concur's account schema. > **Note** > > The name of the account schema attribute must be same as the key in jsonPathMapping. Example of schema attribute names for custom fields: - customData.custom17 - customData.orgUnit1 - report.approver - adp.companyCode ## Default Entitlement Attributes Entitlement attributes define the entitlements, such as groups or roles, that can be assigned to the managed system's user accounts. Refer to [Managing Entitlements]() for more information. > [!CAUTION] > > Changing the attribute marked as the Entitlement ID after aggregating accounts or entitlements can result in duplicate entitlements being created, or access profiles and roles breaking. To avoid this, edit the entitlement schema before performing any aggregations. ### Default Role Attributes The SAP Concur 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 Code | The role's unique identifier. | | Role Name | The role's full name. | | Description | The role's usage. | # 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](). ## InvalidRequestException Error Message While Creating the Account ```text openconnector.InvalidRequestException: [ InvalidRequestException ] [ Possible suggestions ] Please check if provided payload has valid attributes [ Error details ] Error while performing operation : Create Account Error code : 400 {"status":400,"schemas":["urn:ietf:params:scim:api:messages:2.0:Error","urn:ietf:params:scim:api:messages:concur:2.0:Error"],"urn:ietf:params:scim:api:messages:concur:2.0:Error":{"messages":[{"code":"BAD_REQUEST"}]},"detail":"Username does not end with '@' followed by the company domain."} ``` **Resolution**: Ensure the 'Login Name' is provided with correct format and includes the company domain. For example, `firstname.lastname@yourcompanydomainname.com/uat`