Integrate the IAS REST API by Destination Service and Consume in Freestyle UI5 App

[kcezar]

Hi folks,

I want to develop a user registration application to be accessed via Launchpad Service and use a database of IAS feeding 3 custom attributes. However, I'm having difficulties consuming the destination inside of ui5 freestyle application. Do you have an example of an application working with this scenario and the destination properly configured?

I tried combining two tutorials to consume IAS API by Destination Service.

Integrate the REST API via Destination Service:

Integrate Tutorial

In this tutorial, he creates a credential key for the instance created through the API.
Then create the application and use a destination service for the application in the MTA.

It declares that it is needed in the HTML module, and puts a destination route that will be created below.

After the application is deployed, it goes inside the destination service and creates the destination using the credentials created in the first step, giving the same name as the one placed in the route above.

IAS Instance and Key:

IAS Destination Service:

Destination route on xs-app.json:

Destination created inside of Destination Service:

Declare the proxy inside of ui5-local.yaml to consume in the test locally.

Try to consume the service:

The erro:

I create the IAS Instance Service by watching a denys.kempen microlearning:

Denys Hands-on Video Tutorials - openSAP Microlearning

I will be gratefull in advance for everyone that willingness to contribute to my technical growth and continuous improvement. In the scenario I mentioned above, I still can't consume the IAS API.

[Raghu]

Hello,

You may require a sample application like Document Centric Approval Process. This has integration with SCIM APIs.

Kindly refer the resources

SAP Discovery Center Mission

Source Code

The configuration guide and source code will give you an idea how to make this work

[kcezar]

Hi raghuraman.ramakrishnan

I want to thank you for your contribution, it helped a lot. I finally managed to consume the service. But not using destination service integration. The code you provided in your comment helped with what was missing using the Basic Authentication.

But I'm surprised that in this code I find code snippets that I wouldn't expect to find in best-practice applications.

When we declare destination routes and map our destinations, I hope to use them without having to manually fetch the application module.

In my view it doesn't make much sense, the route manager should do this automatically. In the same application, I have odata services with their destination mapped and I don't need to create the base URL application module so that the request can be made through the binding.

I really don't know if I'm done with this workaround. What purpose is to understand the API consumption by the API integration with the destination service. As consumed by Adobe up there.

I'll wait a little longer, if no one in the community knows how this actually works, I'll accept your answer as correct as a thank you.

[r00k13d3v]

Hi Kéfren,

I think it could be because of two things, the first is that in the call I think you have to add / at the beginning of the url and the second is that the authentication method against the IAS is basic auth.

I add a working example in case it helps you.

distination

approuter

request from index.html

Greetings!

[kcezar]

Hi r00k13d3v ,
I've done it this way before. But to confirm your hypothesis I did the steps here.

To make sure there is no problem with the proxy middleware, I deployed it, updated the content provider, and opened it in the Launchpad service. Did not work. The approach I'm taking is following the integration documentation I showed you at the beginning.