You can configure basic, authorization code, and client credentials authentication types to connect to OData V4-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
Use basic authentication to connect to SAP S/4HANA applications. You need the SAP account user name and password to configure basic authentication.
Get the required details from the SAP S/4HANA application to which you want to connect.
For more information about basic authentication in SAP, see Basic authentication in the SAP documentation.
Authorization code
Use OAuth 2.0 authorization code authentication to connect to SAP Datasphere and SAP S/4HANA applications. You need the SAP client ID, client secret, authorization token URL, access token URL, and access token to configure OAuth 2.0 authorization code authentication.
Connecting to SAP Datasphere applications
To connect to SAP Datasphere applications using OAuth 2.0 authorization code authentication, you need to complete certain prerequisite tasks.
Create an authorization integration in SAP, and 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 a 401 error code, the 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.
Connecting to SAP S/4HANA applications
To connect to SAP S/4HANA applications using OAuth 2.0 authorization code authentication, you need to complete certain prerequisite tasks.
•Create an authorization integration in SAP, and 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 a 401 error code, the 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
Use OAuth 2.0 client credentials authentication to connect to SAP S/4HANA applications. You need the SAP client ID, client secret, access token URL, scope, and access token to configure OAuth 2.0 client credentials authentication.
To use OAuth 2.0 client credentials authentication, you need to complete certain prerequisite 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: