OData V2 Protocol Reader Connector > Connections for OData V2 Protocol Reader > OData V2 Protocol Reader connection properties
  

OData V2 Protocol Reader connection properties

When you set up an OData V2 Protocol Reader connection, you must configure the connection properties.
The following table describes the OData V2 Protocol Reader connection properties:
Connection 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 the 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.
Service Type
The service type of the OData V2 application endpoint to which you want to connect.
Choose one of the following service types:
  • - SAP S/4HANA Catalog. Use the SAP S/4HANA Catalog service type for endpoints such as SAP S/4HANA that exposes specialized OData V2 service to list the services present in the endpoint.
  • - Default. Use the Default service type for all other endpoints.
Service URL
The service URL for the selected OData V2 service type.
For the Default service type, enter the root URL of the service.
For example, enter the service URL in the following format:
https://sandbox.api.sap.com/s4hanacloud/sap/opu/odata/sap/API_CHARTOFACCOUNTS_SRV
You can verify if the URL is valid by appending $metadata to the URL.
For SAP S/4HANA catalog service type, enter the URL of the catalog service in SAP S/4HANA.
For example, to access the data from the SAP S/4HANA catalog service, enter the service URL in the following format:
http://<hostname of the OData server>:<port number>/sap/opu/odata/iwfnd/CATALOGSERVICE;v=2/
If the host name and port number is inpha1.informatica.com:8001 and the service endpoint is SAP S/4HANA Catalog, enter the following URL:
https://inpha1.informatica.com:8001/sap/opu/odata/iwfnd/CATALOGSERVICE;v=2/
Authentication Type
The type of user authentication to connect to the OData service.
Choose from the following authentication types:
  • - Basic. Requires the user name and password to log in to the OData V2 application.
  • - API Key. Requires a unique API key to connect to the OData V2 application.
  • - OAuth 2.0 authorization code. Requires authorized access to connect to the OData V2 endpoint.
  • - OAuth 2.0 client credentials. Requires client credentials to connect to the OData V2 endpoint.
Username
Applies to basic authentication.
The user name to connect to the OData V2 application.
Password
Applies to basic authentication.
The password associated with the OData V2 application user name.
API Key
Applies to API key authentication.
Unique API key required to connect to the OData V2 application.

Authorization code authentication

To use authorization code authentication, you must first register the following Informatica redirect URL in your application:
https://<Informatica cloud hosting facility for your organization>/ma/proxy/oauthcallback
If the access token expires and the response returns 401 error code, Informatica redirect URL, which is outside the customer firewall, tries to connect to the endpoint and retrieve a new access token.
The following table describes the OData V2 Protocol Reader connection properties for an OAuth 2.0 authorization code authentication type connection:
Connection property
Description
Runtime Environment
Name of the runtime environment where you want to run the tasks.
Specify a Secure Agent, Hosted Agent, or serverless runtime environment.
Auth Type
The authentication method that the connector must use to connect to the OData V2 endpoint.
Select OAuth 2.0 authorization code.
Default is Basic.
Authorization Token URL
Authorization server URL configured in your application.
Access Token URL
Access token URL configured in your application.
Client ID
The client identifier issued during the application registration process.
Client Secret
The client secret issued during the application registration process.
Scope
The scope of the access request when the OData V2 endpoint has defined custom scopes.
Enter space-separated scope attributes. For example:
ZGWSAMPLE_BASIC_0001 /IWFND/SG_MED_CATALOG_0002 ZAPI_CHARTOFACCOUNTS_SRV_0001
Access Token Parameters
Additional parameters to use with the access token URL.
Define parameters in the JSON format. For example:
[{"Name":"resource","Value":"https://<serverName>"}]
Authorization Code Parameters
Additional parameters to use with the authorization token URL.
Define parameters in the JSON format. For example:
[{"Name":"max_age","Value":60},{"Name":"state","Value":"test"}]
Client Authentication
The client authentication details for authorization.
Select an option to send client ID and client secret for authorization either in the request body or in the request header.
Default is Send client credentials in body.
Generate Access Token
Generates access token and refresh token based on the specified authentication details.
Access Token
The access token granted by the authorization server to access the data using a specific role.
Enter the access token value or click Generate Access Token to populate the access token value.
Refresh Token
Allows the Secure Agent to fetch new access token if the access token is not valid or expires.
Enter the refresh token value or click Generate Access Token to populate the refresh token value.
If the refresh token expires, you must either provide a valid refresh token or click Generate Access Token to regenerate a new refresh token.

Client credential authentication

The following table describes the OData V2 Protocol Reader connection properties for OAuth 2.0 client credentials authentication type connection:
Connection property
Description
Runtime Environment
Name of the runtime environment where you want to run the tasks.
Specify a Secure Agent, Hosted Agent, or serverless runtime environment.
Auth Type
The authentication method that the connector must use to connect to the OData V2 endpoint.
Select OAuth 2.0 client credentials.
Default is Basic.
Access Token URL
Access token URL configured in your application.
Client ID
The client identifier issued during the application registration process.
Client Secret
The client secret issued during the application registration process.
Scope
The scope of the access request when the rest endpoint has defined custom scopes. Enter space-separated scope attributes.
For example:
ZGWSAMPLE_BASIC_0001 /IWFND/SG_MED_CATALOG_0002 ZAPI_CHARTOFACCOUNTS_SRV_0001
Access Token Parameters
Additional parameters to use with the access token URL. Define parameters in the JSON format.
For example:
[{"Name":"resource","Value":"https://<serverName>"}]
Client Authentication
The client authentication details for authorization.
Select an option to send client ID and client secret for authorization either in the request body or in the request header.
Default is Send client credentials in body.
Generate Access Token
Generates access token based on the specified authentication details.
Access Token
The access token granted by the authorization server to access the data using a specific role. Enter the access token value or click Generate Access Token to populate the access token value.