CAP: How to bind to existing XSUAA service on HANA XSA

[kosmopilot]

Hi all,

I have two microservices (NodeJs CAP Apps) running on HANA XSA that need to share the same XSUAA, such that the AuthToken can be forwarded as described in the CAP documentation. One microservice is the consumer that integrates the other microservice as a remote service. Currently, both services use their own XSUAA service with backend & UI5 frontend being bound to.

Assuming that a XSUAA service called my-uaa is already running on the same org & space, what needs to be adjusted in the MTA .yaml of a CAP application such that it binds to my-uaa instead of starting its own XSUAA service?

The current configuration looks like this, which starts its own XSUAA service (consumer-uaa)

[kosmopilot · Accepted solution]

The solution was to change the type of the resource to org.cloudfoundry.existing-service