The configuration of an HTTPS inbound (sender) adapter, including its authentication method, is performed within the design-time environment of an integration flow (iFlow). When setting up OAuth 2.0, you select the adapter on the iFlow canvas and, in its properties, set the 'Authorization' to 'User Role'. This specific configuration is an integral part of the integration flow's definition and is saved and deployed as part of the iFlow artifact. The overall OAuth client setup is done at the tenant level, but the enforcement on a specific endpoint is configured in the iFlow.

A. In the adapter: While you are configuring the adapter's properties, this action occurs within the context of the integration flow editor. The adapter is not a standalone configurable entity outside of an iFlow.

C. In the SAP Integration Suite: This is too general. The SAP Integration Suite is the entire platform, which includes multiple capabilities. The specific configuration happens within the Cloud Integration capability, inside an integration flow.

D. In the process runtime: Configuration is a design-time activity. The process runtime is the environment where the already configured and deployed integration flow is executed.

---

1. SAP Help Portal

SAP Integration Suite Documentation: Configure the Sender HTTPS Adapter.

Section: Procedure

Content: The documentation explicitly states

"You configure the sender HTTPS adapter in an integration flow." It then details the steps

which involve selecting the sender channel within the iFlow editor and setting the 'Authorization' parameter on the 'Connection' tab. This confirms the configuration is an action performed within the integration flow artifact.

2. SAP Help Portal

SAP Integration Suite Documentation: Set Up Inbound HTTP Connections (for API Clients).

Section: OAuth 2.0 Authorization Code Grant

Content: This guide outlines the end-to-end process for setting up OAuth. In step 4

it specifies the required action within the integration artifact: "In your integration flow

configure the sender adapter (for example

HTTPS adapter) to use role-based authorization." This directly links the adapter's security configuration to the integration flow.