Implement token handling and SDM API requests using Cloud SDK#228
Merged
rashmiangadi11 merged 26 commits intodevelopfrom Feb 3, 2026
Merged
Implement token handling and SDM API requests using Cloud SDK#228rashmiangadi11 merged 26 commits intodevelopfrom
rashmiangadi11 merged 26 commits intodevelopfrom
Conversation
![github-code-quality[bot]](https://avatars.githubusercontent.com/u/9919?s=60&v=4){kind=small}
Member
|
@rashmiangadi11, please attach the link of Integration-tests run |
yashmeet29
approved these changes
Feb 3, 2026
Juergen-Goebl-msggroup
pushed a commit
to Andreas-Meindl-msggroup/sdm
that referenced
this pull request
Apr 14, 2026
Implement token handling and SDM API requests using Cloud SDK
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
3 participants
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.
Describe your changes
Standardize token handling and outbound HTTP calls via SAP Cloud SDK. Support user-propagation and technical-user flows, unify REST client usage with resilience, observability, and security best practices. Deliver reusable modules, destination configuration, tests, and documentation.
Any documentation
-This PR creates 2 methods getDestination which returns user token related destination and getTechnicalDestination which returns the technical credentials destination and these destinations are passed to different methods and no need of token as destination has it within even the subdomain.
Removed all the unused token generation code and also updated the unit tests.
Type of change
Please delete options that are not relevant.
Checklist before requesting a review
Upload Screenshots/lists of the scenarios tested
Single tenant
Multitenant
https://github.com/cap-js/sdm/actions/runs/21509535685/job/61972940377
