Introduction
The goal of this series is to introduce the different destination types of the SAP BTP, to show how they work and also to make them tangible with basic and easy to execute code examples. In parts one and two of this series, I looked at t...
Dear community,
currently, I am writing the third part of my blog post series about BTP destination, it will be about Oauth2ClientCredentials destinations. I have already a code sample, this was easy and straight forward, but now I am struggling wi...
Introduction
This series is about taking a closer look at the different destination types of the SAP BTP Cloud Foundry environment and making them more tangible with executable code examples. In the first part, we addressed the underlying motivation ...
Motivation
We are in the midst of the age of cloud computing and the change in IT system landscapes and software development projects is both noticeable and irreversible. Large, heavyweight monoliths are no longer in vogue, IT systems are becoming sm...
Hi,
I have the following architecture for my use case that is deployed on SAP BTP Cloud Foundry:
Angular Frontend, Nodejs Backend and an @sap/approuter Application Router, using UAA Service for Authentication and Authorization purposes. As far as...
Hi carlos.roggan,thanks a lot for your feedback and for the provided links, I will definitely have a look into them. Actually, I guess most of my destination knowledge is based on other blog posts from you about token exchange etc Regards,Jakob
Hi carlos.roggan ,thanks a lot for your very detailed explanation. This definitely helps a lot. So, to summarize, in terms of running services there is one XSUAA server and all the XSUAA services in the CF spaces, are, as you wrote, OAuth Clients, I...
Hi martinstenzig
unfortunately, I have not yet used this kind of destination. I have implemented a mailing functionality in one of my recent projects, but without a destination, but plain nodemailer implementation. Not sure what exactly you want to ...
Hi,Is it possible that the problem is occurring again? We are currently experiencing the same issue, also rolling back to version 4.9.2 has no effect. Is there any additional configuration required to make it running on localhost?Regards,Jakob
