Concur V2 Connector > Concur V2 Connections > Concur V2 connection properties
  

Concur V2 connection properties

When you set up a Concur V2 connection, you can specify Oauth 2 or consumer key authentication to authenticate users and authorize access to Concur data. Informatica recommends that you use the Oauth 2 connection type.
The following table describes the basic connection properties
Property
Description
Connection Name
Name of the connection.
Each connection name must be unique within the organization. Connection names can contain alphanumeric characters, spaces, and the following special characters: _ . + -,
Maximum length is 255 characters.
Description
Description of the connection. Maximum length is 4000 characters.
Use Secret Vault
Stores sensitive credentials for this connection in the secrets manager that is configured for your organization.
This property appears only if secrets manager is set up for your organization.
When you enable the secret vault in the connection, you can select which credentials that the Secure Agent retrieves from the secrets manager. If you don't enable this option, the credentials are stored in the repository or on a local Secure Agent, depending on how your organization is configured.
Note: If you’re using this connection to apply data access policies through pushdown or proxy services, you cannot use the Secret Vault configuration option.
For information about how to configure and use a secrets manager, see Secrets manager configuration.
Runtime Environment
The name of the runtime environment where you want to run tasks.
Select a Secure Agent, Hosted Agent, serverless, or elastic runtime environment.
For more information about how to configure and use the runtime environments, see Runtime environments.
Authentication
Authentication method for the connection.
Ensure that you select Concur V2 for the connection.
User name
The user name to log in to the Concur web page.
Password
The password associated with the user name.
Use Oauth 2
Uses OAuth 2 to authenticate users and authorize access to Concur data.
Select OAuth 2. If you do not select OAuth 2, the connection uses consumer key authentication.
Get the OAuth 2 credentials from SAP Concur.
Base URL for authentication
The URL for authentication that you received from Concur when you created your account.
The base URL for authentication is derived from the authorization URL.
For example, if the authorization URL is https://us-impl.api.concursolutions.com/oauth2/v0/token, the base URL for authentication is https://us-impl.api.concursolutions.com.
Base URL for API Invocation
The URL for API invocation that you received from Concur when you created your account.
Client ID
The unique ID of your application to complete the OAuth Authentication in the Active Directory.
Secret ID
The password of your application to complete the OAuth Authentication in the Active Directory.
Folder
The relative path to the objects that you want to access from Concur.
For example, if the URL for API invocation is https://us-impl.api.concursolutions.com and the absolute path to invoke the API to retrieve the expense reports from Concur is https://us-impl.api.concursolutions.com/api/expense/report, enter the following relative path: expense/report
The following table describes the advanced connection properties:
Property
Description
Consumer Key
The key that is generated when a Concur administrator registers a partner application for your organization.
To use consumer key authentication, ensure that you specify the user name and password of the Concur account in the connection properties.
Note: Informatica intends to drop consumer key authentication support in a future release. Informatica requests you to transition to use OAuth authentication before the consumer key authentication is dropped.