<?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>topic Re: Kyma Environment Variables in Open Source Discussions</title>
    <link>https://community.sap.com/t5/open-source-discussions/kyma-environment-variables/m-p/12721061#M50</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;As a 1st step you might want to try out the code snippet from this &lt;A href="https://blogs.sap.com/2022/04/07/veridisquo.-reaching-sap-lob-destinations-with-connectivity-proxy-and-principal-propagation./" target="_blank"&gt;blog&lt;/A&gt; in a kyma function as a way to validate your setup and connectivity. You will need your bearer token as an argument to the function call; &lt;/P&gt;&lt;P&gt;also please make sure your destination definition looks similar to this &lt;A href="https://gist.github.com/ptesny/203fed6c3b059f5880595d92113669af#file-task1-md" target="_blank"&gt;one&lt;/A&gt;&lt;/P&gt;&lt;P&gt;I hope that helps; kind regards; Piotr&lt;/P&gt;&lt;P&gt;ps. Also looking at the screenshots you have provided. The connectivity proxy secret must not be used by the business application. The on-premise destination must work; that's for sure; however all the business logic wants is the connectivity proxy endpoint as described &lt;A href="https://gist.github.com/ptesny/203fed6c3b059f5880595d92113669af#file-connectivity-proxy-md" target="_blank"&gt;here&lt;/A&gt;&lt;/P&gt;</description>
    <pubDate>Thu, 02 Feb 2023 11:04:09 GMT</pubDate>
    <dc:creator>quovadis</dc:creator>
    <dc:date>2023-02-02T11:04:09Z</dc:date>
    <item>
      <title>Kyma Environment Variables</title>
      <link>https://community.sap.com/t5/open-source-discussions/kyma-environment-variables/m-p/12721060#M49</link>
      <description>&lt;P&gt;&lt;A href="https://www.npmjs.com/package/@sap/xsenv" target="test_blank"&gt;https://www.npmjs.com/package/@sap/xsenv&lt;/A&gt;&lt;/P&gt;
  &lt;P&gt;xsuaa&lt;/P&gt;
  &lt;P&gt;&lt;IMG class="migrated-image" src="https://community.sap.com/legacyfs/online/storage/attachments/storage/7/attachments/2137507-image.png" /&gt;&lt;/P&gt;
  &lt;P&gt;destination instance&lt;/P&gt;
  &lt;P&gt;&lt;IMG class="migrated-image" src="https://community.sap.com/legacyfs/online/storage/attachments/storage/7/attachments/2137505-image.png" /&gt;&lt;/P&gt;
  &lt;P&gt;destination binding&lt;/P&gt;
  &lt;P&gt;&lt;IMG class="migrated-image" src="https://community.sap.com/legacyfs/online/storage/attachments/storage/7/attachments/2137508-image.png" /&gt;&lt;/P&gt;
  &lt;P&gt;connectivity proxy binding&lt;/P&gt;
  &lt;P&gt;&lt;IMG class="migrated-image" src="https://community.sap.com/legacyfs/online/storage/attachments/storage/7/attachments/2137504-image.png" /&gt;&lt;/P&gt;
  &lt;P&gt;connectivity proxy binding&lt;/P&gt;
  &lt;P&gt;&lt;IMG class="migrated-image" src="https://community.sap.com/legacyfs/online/storage/attachments/storage/7/attachments/2137503-image.png" /&gt;&lt;/P&gt;
  &lt;P&gt;deployment&lt;/P&gt;
  &lt;P&gt;&lt;IMG class="migrated-image" src="https://community.sap.com/legacyfs/online/storage/attachments/storage/7/attachments/2137502-image.png" /&gt;&lt;/P&gt;
  &lt;P&gt;call destination&lt;/P&gt;
  &lt;P&gt;&lt;IMG class="migrated-image" src="https://community.sap.com/legacyfs/online/storage/attachments/storage/7/attachments/2137501-image.png" /&gt;&lt;/P&gt;
  &lt;P&gt;get token&lt;/P&gt;
  &lt;P&gt;&lt;IMG class="migrated-image" src="https://community.sap.com/legacyfs/online/storage/attachments/storage/7/attachments/2137509-image.png" /&gt;&lt;/P&gt;
  &lt;P&gt;test &lt;/P&gt;
  &lt;PRE&gt;&lt;CODE&gt;curl --location --request GET 'https://conexao-cloud-conector-s4.c-71b475b.kyma.ondemand.com/' \ --header 'Authorization: Bearer &amp;lt;access_token&amp;gt;'&lt;/CODE&gt;&lt;/PRE&gt;
  &lt;P&gt;error:&lt;/P&gt;
  &lt;P&gt;&lt;IMG class="migrated-image" src="https://community.sap.com/legacyfs/online/storage/attachments/storage/7/attachments/2137500-image.png" /&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 01 Feb 2023 23:21:05 GMT</pubDate>
      <guid>https://community.sap.com/t5/open-source-discussions/kyma-environment-variables/m-p/12721060#M49</guid>
      <dc:creator>LuizGomes</dc:creator>
      <dc:date>2023-02-01T23:21:05Z</dc:date>
    </item>
    <item>
      <title>Re: Kyma Environment Variables</title>
      <link>https://community.sap.com/t5/open-source-discussions/kyma-environment-variables/m-p/12721061#M50</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;As a 1st step you might want to try out the code snippet from this &lt;A href="https://blogs.sap.com/2022/04/07/veridisquo.-reaching-sap-lob-destinations-with-connectivity-proxy-and-principal-propagation./" target="_blank"&gt;blog&lt;/A&gt; in a kyma function as a way to validate your setup and connectivity. You will need your bearer token as an argument to the function call; &lt;/P&gt;&lt;P&gt;also please make sure your destination definition looks similar to this &lt;A href="https://gist.github.com/ptesny/203fed6c3b059f5880595d92113669af#file-task1-md" target="_blank"&gt;one&lt;/A&gt;&lt;/P&gt;&lt;P&gt;I hope that helps; kind regards; Piotr&lt;/P&gt;&lt;P&gt;ps. Also looking at the screenshots you have provided. The connectivity proxy secret must not be used by the business application. The on-premise destination must work; that's for sure; however all the business logic wants is the connectivity proxy endpoint as described &lt;A href="https://gist.github.com/ptesny/203fed6c3b059f5880595d92113669af#file-connectivity-proxy-md" target="_blank"&gt;here&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 02 Feb 2023 11:04:09 GMT</pubDate>
      <guid>https://community.sap.com/t5/open-source-discussions/kyma-environment-variables/m-p/12721061#M50</guid>
      <dc:creator>quovadis</dc:creator>
      <dc:date>2023-02-02T11:04:09Z</dc:date>
    </item>
    <item>
      <title>Re: Kyma Environment Variables</title>
      <link>https://community.sap.com/t5/open-source-discussions/kyma-environment-variables/m-p/12721062#M51</link>
      <description>&lt;P&gt;&lt;A href="https://gist.github.com/ptesny/203fed6c3b059f5880595d92113669af#file-task1-md" target="test_blank"&gt;https://gist.github.com/ptesny/203fed6c3b059f5880595d92113669af#file-task1-md&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Do I have to assemble this information by hand? Is this not compatible with any SAP package used to connect from BTP to S4 via cloud connector, for example sap-cloud-sdk?&lt;/P&gt;</description>
      <pubDate>Thu, 02 Feb 2023 21:25:05 GMT</pubDate>
      <guid>https://community.sap.com/t5/open-source-discussions/kyma-environment-variables/m-p/12721062#M51</guid>
      <dc:creator>LuizGomes</dc:creator>
      <dc:date>2023-02-02T21:25:05Z</dc:date>
    </item>
    <item>
      <title>Re: Kyma Environment Variables</title>
      <link>https://community.sap.com/t5/open-source-discussions/kyma-environment-variables/m-p/12721063#M52</link>
      <description>&lt;P&gt;hello, this is what you can read in the cloud-sdk documentation: &lt;A href="https://sap.github.io/cloud-sdk/docs/js/guides/kubernetes#on-premise-connectivity" target="test_blank"&gt;https://sap.github.io/cloud-sdk/docs/js/guides/kubernetes#on-premise-connectivity&lt;/A&gt;&lt;/P&gt;&lt;P&gt;I hope that helps; kind regards; Piotr&lt;/P&gt;</description>
      <pubDate>Thu, 02 Feb 2023 22:33:02 GMT</pubDate>
      <guid>https://community.sap.com/t5/open-source-discussions/kyma-environment-variables/m-p/12721063#M52</guid>
      <dc:creator>quovadis</dc:creator>
      <dc:date>2023-02-02T22:33:02Z</dc:date>
    </item>
  </channel>
</rss>

