## 5.6.2.2.4 Communication Arrangement JSON File Examples
The examples in this section will help you to create the service JSON descriptor used for defining the communication arrangement and the authentication type for the SAP S/4HANA Cloud API access.
The information that you need to create the JSON file is available in the Display Communication Scenario app in the corresponding SAP S/4HANA Cloud system. It contains information such as scenario details and properties, and supported inbound and outbound authentication methods. See Display Communication Scenarios.
##  Note
The purpose of these examples is just to give you an idea how you construct your JSON file. For more details of the properties of these JSON files, see Communication Arrangement JSON/YAML File Properties [page 2121].
## Example of Enabling Communication Scenario of Type Basic Authentication
This is an example of a JSON file for a communication arrangement with an inbound connection with Basic Authentication and an outbound connection with Basic Authentication .
```
{ "systemName": "DEMO", "communicationArrangement": { "communicationArrangementName": "INBOUND_COMMUNICATION_ARRANGEMENT", "scenarioId": "SAP_COM_0008", "inboundAuthentication": "BasicAuthentication", "outboundAuthentication": "BasicAuthentication", "outboundServices": [ { "id": "DEBMAS_IDOC", "isServiceActive": false }, { "id": "CREMAS_IDOC", "isServiceActive": false }, { "id": "ADRMAS_IDOC", "isServiceActive": false }, { "id": "ADR3MAS_IDOC", "isServiceActive": false }, { "id": "ADR2MAS_IDOC", "isServiceActive": false }, { "id": "CO_MDG_BP_RPLCTRQ_SPRX", "isServiceActive": false }, { "id": "CO_MDG_BP_RELATIONSHIP_OUT_SPRX", "isServiceActive": false }, { "id": "CO_MDG_BP_RPLCTCO_SPRX", "isServiceActive": false }, { "id": "CO_MDG_BP_RELATIONSHIP_CNF_OUT_SPRX", "isServiceActive": false } ], "communicationSystem": { "communicationSystemHostname": "default.com", "outboundCommunicationUser": { "username": "DefaultUser", "password": "DefaultPassword" } } } }
```
## Example of Enabling Communication Scenario of Type OAuth2ClientCredentials
This is an example of a JSON file for a communication arrangement with an outbound connection with authentication type OAuth2ClientCredentials .
```
{ "systemName":"DEMO", "communicationArrangement":{ "outboundAuthentication":"OAuth2ClientCredentials", "communicationArrangementName":"0219_ARRANGEMENT", "scenarioId":"SAP_COM_0219", "communicationSystem":{ "communicationSystemHostname":"default.com", "oAuthAuthEndpoint":"oauth.com/oauth/authorize", "oAuthTokenEndpoint":"oauth.com/oauth/token", "outboundCommunicationUser":{ "username":"DefaultUser", "password":"DefaultPassword" } } } }
```
## Example for Enabling Communication Scenario of Type OAuth2SAMLBearerAssertion
This is an example of a JSON file for a communication arrangement with an inbound connection with OAuth2SAMLBearerAssertion and an outbound connection with NoAuthentication .
To communicate with SAP S/4HANA Cloud the extension application can use Principal Propagation which is done using OAuth 2.0 SAML Bearer Assertion flows. Principal Propagation means you forward the identity of the logged-in cloud users when accessing or updating data in the SAP S/4HANA Cloud system.
This is useful in scenarios where you need to have restricted data access based on the logged-in user from your extension. Or, you want to ensure only users with the right permissions are able to update the system via extensions deployed in SAP BTP, Cloud Foundry runtime.
```
{ "systemName": "DEMO", "communicationArrangement": { "scenarioId": "SAP_COM_0213", "communicationArrangementName": "0213_ARRANGEMENT", "inboundAuthentication": "OAuth2SAMLBearerAssertion", "communicationSystem": { "communicationSystemHostname": "default.com" } } }
```
## Example for Enabling Communication Scenario of Type NoAuthentication
This is an example of a JSON file for a communication arrangement with an outbound connection with authentication type NoAuthentication .
```
{ "systemName": "DEMO", "communicationArrangement": { "outboundAuthentication": "NoAuthentication", "communicationArrangementName": "0215_ARRANGEMENT", "scenarioId": "SAP_COM_0215", "outboundServices": [ { "id": "SAP_COM_0215_0001_REST", "isServiceActive": true } ], "communicationSystem": { "communicationSystemHostname": "default.com" } } }
```
## Example for Enabling Communication Scenario of Type Client Certificate Authentication with Inbound Connection
This is an example of a JSON file for a communication arrangement with an inbound connection with authentication type ClientCertificateAuthentication .
```
{ "systemName": "DEMO", "communicationArrangement": { "scenarioId": "SAP_COM_0724", "communicationArrangementName": "CommunicationArrangementName", "inboundAuthentication": "ClientCertificateAuthentication" } }
```
## Example for Enabling Communication Scenario of Type Client Certificate Authentication with Outbound Connection
This is an example of a JSON file for a communication arrangement with an outbound connection with authentication type ClientCertificateAuthentication .
```
{ "systemName": "DEMO", "communicationArrangement": { "communicationArrangementName": "CommunicationArrangementName", "scenarioId": "SAP_COM_0047", "outboundAuthentication": "ClientCertificateAuthentication", "communicationSystem": { "communicationSystemHostname": "default.com"
```
```
} } }
```
## Example for Enabling Communication Scenario of Type OAuth2mTLS
This is an example of a JSON file for a communication arrangement with an outbound connection with authentication type OAuth2mTLS .
```
{ "systemName": "DEMO", "communicationArrangement": { "outboundAuthentication": "OAuth2mTLS", "communicationArrangementName": "CommunicationArrangementName", "scenarioId": "SAP_COM_0080", "communicationSystem": { "communicationSystemHostname": "default.com", "oAuthAuthEndpoint":"oauth.com/oauth/authorize", "oAuthTokenEndpoint":"oauth.com/oauth/token", "outboundCommunicationUser": { "username": "DefaultUser" } } } }
```