When SAP Cloud Platform Integration sends messages to systems, SAP Cloud Platform Integration (f.k.a HCI) must be authenticated by the receiving systems. In this blog, we shall see the types of authentication and how to do it. This blog is a part of the series on Understanding Authentication & Testing Connectivity in SAP Cloud Platform Integration. You can access all the blogs here.
You can authenticate from SAP Cloud Platform Integration to other systems using certificate-based authentication, basic authentication or the OAuth 2.0 authentication. SAP Cloud Platform Integration has a uniform way of configuring the authentication – through the use of Credential Artifacts.
(A small note: The complete OAuth 2.0 specification is not yet supported. We currently support only the client credentials grant type.)
How to configure Authentication Credentials?
In the Eclipse tool-set, navigate to the Deployed Artifacts tab of the tenant. Click on the Deploy button and select the type of authentication from the wizard. The procedure is illustrated below:
For example, you let’s say you want to send messages to an SAP Cloud for Customer application and want to authenticate using the credentials of the Cloud for Customer application. In the Deploy Artifacts wizard, you select the User Credentials artifact, specify a username and password. This credential artifact is then referred in the sender channel of the integration flow. A sample configuration is provided below:
When you want to authenticate from SAP Cloud Platform Integration, always maintain the authentication information in the credential artifacts. An inherent advantage of this mechanism of SAP Cloud Platform Integration is that you have to maintain the credentials of a receiving system only in one artifact; you can refer to the same artifact in multiple integration flows. Further, if you have to change the authentication details – you have to do it only once and need not reconfigure the integration flows.