Skip to content

docs: clarify auth type scoping for ABAP Cloud destinations #155

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
longieirl merged 1 commit into from
May 20, 2026
Merged

docs: clarify auth type scoping for ABAP Cloud destinations #155

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 6 additions & 2 deletions misc/abapcloud/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -46,11 +46,13 @@ The destination must point to the ABAP system root URL with no service path appe
- `HTML5.DynamicDestination`: `true`
- Correct root URL with no service path appended
- Proper authentication type based on the scenario:
- Same subaccount: `OAuth2UserTokenExchange`
- Cross-subaccount: `SAMLAssertion`
- Same subaccount: `OAuth2UserTokenExchange` or `SAMLAssertion`
- Cross-subaccount (requires trust between subaccounts): `SAMLAssertion`

The following is an example of an `OAuth2UserTokenExchange` destination for an ABAP Cloud system (same-subaccount scenario):

> **Note**: `OAuth2UserTokenExchange` is only applicable when the destination is configured in the same subaccount that hosts the ABAP Cloud instance. For cross-subaccount or cross-region scenarios, use `SAMLAssertion` instead. See [Enable an SAP BTP Destination for Usage Across Global Accounts or Between Different Regions Using SAMLAssertion](#enable-an-sap-btp-destination-for-usage-across-global-accounts-or-between-different-regions-using-samlassertion).

```json
{
"Authentication": "OAuth2UserTokenExchange",
Expand All @@ -75,6 +77,8 @@ The following is an example of an `OAuth2UserTokenExchange` destination for an A

Alternatively, `SAMLAssertion` can be used for both same-subaccount and cross-subaccount scenarios. The following is an example:

> **Note**: `SAMLAssertion` works on the same subaccount that hosts the ABAP Cloud instance without any additional trust configuration. When used across subaccounts, both subaccounts must be under the same global account and trust must be established between them — the signing certificate from the source subaccount must be imported into the target ABAP Cloud system. See [Cross-Subaccount Requirements](#cross-subaccount-requirements).

```json
{
"Authentication": "SAMLAssertion",
Expand Down
Loading