Q: 6
Where must you configure an HTTPS inbound adapter with OAuth 2.0 authentication?
Options
Discussion
Option B makes sense here. The adapter's OAuth 2.0 settings actually go into the iFlow itself, not the global Integration Suite config. Tenant-wide OAuth is more C, but this one asks about adapter config specifically. If anyone got a different scenario on their test let me know.
B. not A. The OAuth setup for HTTPS inbound adapter is configured directly inside the iFlow, that's how you control auth per flow. Pretty sure that's what SAP expects here but open to other thoughts if I'm missing a twist.
Option B is what SAP highlights, also matches what you'll find in the official documentation and practice sets.
Isn't it C since OAuth 2.0 configs are managed in the Integration Suite?
B seems right since the HTTPS inbound adapter gets its OAuth config in each integration flow, not at a global or runtime spot. C is more about overall settings, but the adapter-specific part happens in the iFlow. Pretty confident but always room for SAP twists.
You do this in the integration flow, so B. Each iFlow handles its own inbound adapter config, not a global adapter setting.
Makes sense that it's B for configuring OAuth 2.0 at the iFlow level. The adapter settings you see are actually part of the flow definition, not a global adapter setting. Pretty sure that's what SAP expects here, but correct me if you see it otherwise.
A or B? I always thought OAuth 2.0 for HTTPS adapters could be set in the adapter config itself, not just at the iFlow level. Maybe I'm missing something, but A seems plausible if you interpret "adapter" as the actual config step. Anyone see it differently?
I don't think it's A. B is correct here since adapter settings like OAuth for incoming HTTPS are configured within the integration flow. Option A is a common trap, but the actual config happens in the iFlow design, not on the adapter itself directly.
Why not C? Does config here mean OAuth client registration or just where you assign OAuth in the adapter?
Be respectful. No spam.
