event-broker: add xsuaa-cross-consumption (#1341)

Co-authored-by: René Jeglinsky <[email protected]>
cap-js · Oct 18, 2024 · 4bf21c7 · 4bf21c7
1 parent a8b4617
commit 4bf21c7
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 0 deletions.
diff --git a/guides/messaging/event-broker.md b/guides/messaging/event-broker.md
@@ -89,6 +89,7 @@ Please see [Deploy to Cloud Foundry](../deployment/to-cf) regarding deployment w
 ### Connecting it All Together
 
 In SAP BTP System Landscape, add a new system of type `SAP BTP Application` for your CAP application including its integration dependencies, connect all involved systems (incl. SAP Cloud Application Event Hub) into a formation and enable the event subscription.
+
 For more details, please refer to guide [CAP Application as a Consumer](https://help.sap.com/docs/event-broker/event-broker-service-guide/cap-application-as-subscriber) in the official documentation of SAP Cloud Application Event Hub.
 
 ::: tip Test Events

diff --git a/node.js/messaging.md b/node.js/messaging.md
@@ -495,6 +495,7 @@ resources:
       config:
         consumed-services:
           - service-instance-name: incidents-event-broker
+       	xsuaa-cross-consumption: true #> if token exchange from IAS token to XSUAA token is needed
         display-name: cap.incidents #> any value, e.g., reuse MTA ID
         home-url: ~{incidents-srv-api/url}
 ```