<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>Question Re: Using a Single App Router for Multiple CAP Services in Technology Q&amp;A</title>
    <link>https://community.sap.com/t5/technology-q-a/using-a-single-app-router-for-multiple-cap-services/qaa-p/14015714#M4904209</link>
    <description>&lt;P&gt;Hi Brian,&lt;/P&gt;&lt;P&gt;This should be perfectly possible since the approuter and the CAP service application are 2 distinct applications in any case. So whether it's a single CAP service application or multiple shouldn't really matter.&lt;/P&gt;&lt;P&gt;The approuter is responsible of getting the user authenticated against the bound xsuaa service instance. Then it will route requests to the correct destination (CAP service application) based on the route. Note that these destinations are configured with 'no authentication', basically meaning that the token that the approuter gives it, should suffice to gain access to the CAP service. This implies that each CAP service should rely on the exact same xsuaa service instance, otherwise they won't accept the token.&lt;/P&gt;&lt;P&gt;You could rewire the default destinations to do token exchange as well, but if it's not a problem to use a single xsuaa service instance then this would be the easiest approach.&lt;/P&gt;&lt;P&gt;So just make sure that all applications (approuter + CAP services) are bound to the same xsuaa service instance and that your routes are configured to forward the token (default setting).&lt;/P&gt;&lt;P&gt;If you experience any issues, it would help to post your MTA here, or provide a git with your sample code to explore further.&lt;/P&gt;</description>
    <pubDate>Thu, 13 Feb 2025 05:33:24 GMT</pubDate>
    <dc:creator>Willem_Pardaens</dc:creator>
    <dc:date>2025-02-13T05:33:24Z</dc:date>
    <item>
      <title>Using a Single App Router for Multiple CAP Services</title>
      <link>https://community.sap.com/t5/technology-q-a/using-a-single-app-router-for-multiple-cap-services/qaq-p/14015240</link>
      <description>&lt;P&gt;Hello experts,&lt;/P&gt;&lt;P&gt;I hope you are all doing well.&lt;/P&gt;&lt;P&gt;I am currently working on a project where I need to configure a single App Router to handle multiple CAP (Cloud Application Programming) services. While I have successfully managed to use a single App Router for multiple SAPUI5 front-end applications, I am struggling to extend this approach to multiple CAP services.&lt;/P&gt;&lt;P&gt;Despite my research and experimentation, I have not yet found a clear or effective way to achieve this. I would greatly appreciate any guidance, recommendations, or best practices you might have on this matter.&lt;/P&gt;&lt;P&gt;Has anyone here managed to configure an App Router to seamlessly route requests to different CAP services within the same deployment? If so, I would be grateful for any insights or examples you could share.&lt;/P&gt;&lt;P&gt;Many thanks in advance for your help!&lt;/P&gt;</description>
      <pubDate>Wed, 12 Feb 2025 13:08:40 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/using-a-single-app-router-for-multiple-cap-services/qaq-p/14015240</guid>
      <dc:creator>BrianBacarezza</dc:creator>
      <dc:date>2025-02-12T13:08:40Z</dc:date>
    </item>
    <item>
      <title>Re: Using a Single App Router for Multiple CAP Services</title>
      <link>https://community.sap.com/t5/technology-q-a/using-a-single-app-router-for-multiple-cap-services/qaa-p/14015714#M4904209</link>
      <description>&lt;P&gt;Hi Brian,&lt;/P&gt;&lt;P&gt;This should be perfectly possible since the approuter and the CAP service application are 2 distinct applications in any case. So whether it's a single CAP service application or multiple shouldn't really matter.&lt;/P&gt;&lt;P&gt;The approuter is responsible of getting the user authenticated against the bound xsuaa service instance. Then it will route requests to the correct destination (CAP service application) based on the route. Note that these destinations are configured with 'no authentication', basically meaning that the token that the approuter gives it, should suffice to gain access to the CAP service. This implies that each CAP service should rely on the exact same xsuaa service instance, otherwise they won't accept the token.&lt;/P&gt;&lt;P&gt;You could rewire the default destinations to do token exchange as well, but if it's not a problem to use a single xsuaa service instance then this would be the easiest approach.&lt;/P&gt;&lt;P&gt;So just make sure that all applications (approuter + CAP services) are bound to the same xsuaa service instance and that your routes are configured to forward the token (default setting).&lt;/P&gt;&lt;P&gt;If you experience any issues, it would help to post your MTA here, or provide a git with your sample code to explore further.&lt;/P&gt;</description>
      <pubDate>Thu, 13 Feb 2025 05:33:24 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/using-a-single-app-router-for-multiple-cap-services/qaa-p/14015714#M4904209</guid>
      <dc:creator>Willem_Pardaens</dc:creator>
      <dc:date>2025-02-13T05:33:24Z</dc:date>
    </item>
  </channel>
</rss>

