![]() ![]() To do so, a client certificate and key is sent along with the request (instead of user/password i.e. ![]() To fetch the required JWT token, the app sends a request to the IAS which acts as Authorization Server. ![]() (See next blog post how to deal with 2 instances of identity service). It is bound to the same instance of identity service, which acts as OAuth client. The frontend app wants to call the backend app in order to get some data. The app is bound to an instance of identity service which is connected to the IAS tenant. The backend doesn’t care HOW the JWT token was requested. The backend endpoint requires an incoming JWT token for authentication and will validate it. Like all good backends, the endpoint is protected with OAuth. We have a backend application that is meant to be used by other applications in SAP BTP. Just a few words to introduce the focus of the tutorial. In this hands-on tutorial, we’re using the same setup and scenario like in previous tutorial, so please see here for the description. SAP Cloud Identity Services – Identity Authentication (IAS), SAP Business Technology Platform (SAP BTP), Cloud Foundry Environment, The difference to previous tutorial is that this time we’re using a client certificate in order to fetch the access token (mTLS), instead of using basic authentication with clientsecret. We create a minimalistic sample app2app scenario where 2 application communicate with each other while authentication is done with the OAuth flow called “client-credentials”. This blog post shows how to do client-credentials flow with IAS using “identity” service in SAP BTP. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |