You can configure basic, API key, authorization code, and client credentials authentication types to access OData V2-compliant applications in SAP.
Before you configure the connection properties, you need to keep the authentication details handy based on the authentication type that you want to use.
Basic
To connect to SAP OData V2 services using basic authentication, you need the SAP account user name and password.
Get the required details from the SAP application to which you want to connect.
For more information about basic authentication in SAP, see Basic authentication in the SAP documentation.
API key
To connect to SAP OData V2 services using API key authentication, you need a unique API key that SAP OData V2 Connector uses to authenticate the API calls made to the SAP OData endpoint.
Get the API key from the SAP application to which you want to connect.
For more information about how to generate and use an API key, see Add API keys to an environment in the SAP documentation.
Authorization code
To connect to SAP OData V2 services using the OAuth 2.0 authorization code, you need the SAP client ID, client secret, authorization token URL, access token URL, and access token.
Before you use OAuth 2.0 authorization code authentication, complete the following tasks:
•Create an authorization integration in SAP, and register the Informatica redirect URL in SAP Integration Suite.
SAP Integration Suite is an integration platform-as-a-service that enables clients that support OAuth to redirect users to an authorization page and generate access tokens, and optionally, refresh tokens to access SAP.
Register the following Informatica redirect URL in SAP Integration Suite:
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 retrieves a new access token.
For more information about how to create an authorization integration and get the authorization details, see OAuth 2.0 authorization code in the SAP documentation.
•Import the .cer certificate into the cacerts file located in the jdk directory available at one or more of the following locations within your Secure Agent installation:
Ensure to add the certificate to all the available directories.
•If there is a jdk directory within the <Secure agent installation directory>\apps folder, navigate to the following directory and import the .cer certificate into the cacerts file located in the jdk directory available at one or more of the following locations within your Secure Agent installation:
After you import the .cer certificate into the cacerts file, you need to restart the Secure Agent.
Client credentials
To connect to SAP OData V2 services using OAuth 2.0 client credentials, you need the SAP client ID, client secret, access token URL, and access token.
Before you use OAuth 2.0 client credentials authentication, complete the following tasks:
•Configure the OAuth endpoint with the client credentials grant type and then create an authorization integration to get the authorization details in the SAP system.
For more information about how to create an authorization integration and get the authorization details, see OAuth 2.0 client credentials in the SAP documentation.
•Import the .cer certificate into the cacerts file located in the jdk directory available at one or more of the following locations within your Secure Agent installation:
Ensure to add the certificate to all the available directories.
•If there is a jdk directory within the <Secure agent installation directory>\apps folder, navigate to the following directory and import the .cer certificate into the cacerts file located in the jdk directory available at one or more of the following locations within your Secure Agent installation: