docs: clarify auth type scoping for ABAP Cloud destinations#155
Merged
Conversation
Clarify that OAuth2UserTokenExchange is same-subaccount only, and SAMLAssertion works both same-subaccount and cross-subaccount but requires trust established between subaccounts for the latter.
🔗 Link Check ResultsThe link checker has completed. This is an optional check and will not block the PR. If broken links were found, please review them at your convenience. Last updated: Run #223 at 2026-05-19T20:19:45Z |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
OAuth2UserTokenExchangeis only applicable on the same subaccount hosting the ABAP Cloud instanceSAMLAssertionworks same-subaccount and cross-subaccount, but cross-subaccount requires trust established between both subaccountsTest plan