Concur offers two on-demand Software as a Service (SaaS) products to help manage travel. Concur Travel & Expense gives you web and mobile solutions for travel and expense management, and TripIt is a mobile travel organizer for individuals.

Supervisor configuration parameters

To configure the connector, following parameters are required:

• Connector name

• Client Id

• Client Secret

• Username (in v.1.0)

• Password (in v.1.0)

• Geolocation (in v.1.0)

• RefreshToken (in v.2.0)

• Target URL (Cloud application's instance URL used as targetURI in payload)

• Instance DateTime Offset (refer Configuring additional datetime offset in connectors for more details).

Supported objects and operations

Users

Table 186: Supported operations for Users (for v1.0)

Operation	VERB
Create User	POST
Update User	POST
Delete User	DELETE
Get User	GET
Get All Users	GET
Get All Users with Pagination	GET

Table 187: Supported operations for Users (for v2.0)

Operation	VERB
Get User	GET
Get All Users	GET
Get All Users with Pagination	GET
Create User	POST
Update User	PUT

Groups

NA

Mandatory fields

Users (v1.0)

• userName

• name.givenName

• name.familyName

• enterpriseUserExtension.empId

• emails.value

• password

• scimUser.locale

• enterpriseUserExtension.ctryCode

• enterpriseUserExtension.crnKey

• enterpriseUserExtension.ledgerKey

Users (v2.0)

• userName

• name.givenName

• name.familyName

• emails[].value

• emails[].type

• active

• enterpriseUserExtension.companyId

• enterpriseUserExtension.startDate

• entitlements[].value

• roles[].value

• enterpriseUserExtension.employeeNumber

Groups

NA

User and Group mapping

The user and group mappings are listed in the tables below.

Table 188: User mapping

SCIM parameter	Concur parameter
Id	LoginId
userName	LoginId
Name.GivenName	FirstName
name.MiddleName	Mi
Name.FamilyName	LastName
DisplayName	FirstName+LastName
Emails[0].value	EmailAddress
Active	Active
Locale	LocaleName
Extension.EmpId	EmpId
Extension.LedgerKe	LedgerName
Extension.CtryCode	CtryCode
Extension.CrnKey	CrnKey
Extension.ExpenseApprover	ExpenseApprover
Extension.Custom1	Custom1
Extension.Custom2	Custom2
Extension.Custom3	Custom3
Extension.Custom4	Custom4
Extension.Custom5	Custom5
Extension.Custom6	Custom6
Extension.Custom7	Custom7
Extension.Custom8	Custom8
Extension.Custom9	Custom9
Extension.Custom10	Custom10
Extension.Custom11	Custom11
Extension.Custom12	Custom12
Extension.Custom13	Custom13
Extension.Custom14	Custom14
Extension.Custom15	Custom15
Extension.Custom16	Custom16
Extension.Custom17	Custom17
Extension.Custom18	Custom18
Extension.Custom19	Custom19
Extension.Custom20	Custom20
Extension.Custom21	Custom21
Extension.OrgUnit1	OrgUnit1
Extension.OrgUnit2	OrgUnit2
Extension.OrgUnit3	OrgUnit3
Extension.OrgUnit4	OrgUnit4
Extension.OrgUnit5	OrgUnit5
Extension.OrgUnit6	OrgUnit6

Table 189: User v2 mapping

SCIM parameter	Concur parameter
Active	active
Addresses	addresses
DisplayName	displayName
Emails[].value	emails[].value
Extension.CompanyId	extension.companyId
Extension.CostCenter	extension.costCenter
Extension.Department	extension.department
Extension.Division	extension.division
Extension.EmployeeNumber	extension.employeeNumber
Extension.Manager.value	extension.manager.value
Extension.Organization	extension.organization
Extension.StartDate	extension.startDate
Extension.TerminationDate	extension.terminationDate
externalId	externalId
Id	id
Meta.Created	meta.created
Meta.LastModified	meta.lastModified
Name.FamilyName	name.familyName
Name.GivenName	name.givenName
name.MiddleName	name.middleName
NickName	nickName
PhoneNumbers	phoneNumbers
PreferredLanguage	preferredLanguage
TimeZone	timezone
Title	title
UserName	userName
Roles[].value	spendExtensionRole.roles[].roleName
Roles[].display	spendExtensionRole.roles[].roleName
Entitlements[].value	entitlements[]
Entitlements[].display	entitlements[]
Extension.SpendReimbursementCurrency	spendExtensionUser.reimbursementCurrency
Extension.SpendLocale	spendExtensionUser.locale
Extension.SpendCountry	spendExtensionUser.country
Extension.SpendLedgerCode	spendExtensionUser.ledgerCode
extension.primaryApprover.id	SpendApprover.report[].approver.value
extension.primaryApprover.userName	UserName
extension.primaryApprover.employeeNumber	Extension.EmployeeNumber

Groups

NA

Connector limitations

• Connector will not return inactive users in the Get All Users response and return 404 Not Found for Get User by Id. (returned in version v.2.0)

• Meta data information with created and lastModified dates are not supported. (Supported in version v.2.0)

• Create User with the details of an existing User will return the same User details with ‘201 Created’. (returns 409 conflict in version v.2.0)

• Update of givenName and familyName are not supported. (Supported in version v.2.0)

• It is required to pass the values in specific format for the custom fields which depends on the target instance.

• To perform a successful integration, the enabled mandatory custom attributes need to be configured in One IM and all the values should be passed accordingly.

The following subsections describe the different connector version(s) and features available with them.

Features available exclusively in Concur v.2.0

Following are the features that are available exclusively in Concur v.2.0:

• v.2.0 of Concur connector leverages v4 APIs of target system.

Connector SCIM configuration

• The Concur connector is enhanced to support the configuration of SCIM connector with custom attributes.

• Disabling the attributes is not supported as this feature is not available in Concur.

• The supported custom attributes are custom 1 through 21 and orgUnit 1 through 6, which are string types.

• Only the "Users" resource type has support for configuring custom attributes via SCIM configuration.

Support for filter condition

• The connector supports filter condition on externalId, companyId, employeeNumber and userName.
• The only filter operator supported is eq.
• Supports AND logical operator only with the attribute combination employeeNumber + companyId and externalId + companyId.
• For OR logical operator, and for any other combination of attributes, the target API returns error message.
• The connector supports only the double quotes in the filter value (ex. userName eq "testUser").