<?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: Call SCP Workflow API from ABAP program in Technology Q&amp;A</title>
    <link>https://community.sap.com/t5/technology-q-a/call-scp-workflow-api-from-abap-program/qaa-p/12189974#M4560053</link>
    <description>&lt;P&gt;Do we have any documents for Cloud Foundry ?&lt;/P&gt;</description>
    <pubDate>Wed, 04 May 2022 02:37:34 GMT</pubDate>
    <dc:creator>quyen_sap_viet</dc:creator>
    <dc:date>2022-05-04T02:37:34Z</dc:date>
    <item>
      <title>Call SCP Workflow API from ABAP program</title>
      <link>https://community.sap.com/t5/technology-q-a/call-scp-workflow-api-from-abap-program/qaq-p/12189967</link>
      <description>&lt;P&gt;Dear experts&lt;/P&gt;
  &lt;P&gt;I need to develop an application that triggers a SCP Workflow api, implementing principal propagation. The application that calls the api is an ABAP report in my on-premise system and user that start the process need to be propagated to cloud.&lt;/P&gt;
  &lt;P&gt;SCP &lt;STRONG&gt;Application Identity Provider&lt;/STRONG&gt; trusts in a custom SAP IAS, &lt;STRONG&gt;so i can't call workflow api using basic authentication, only using SAML 2.0 mode.&lt;/STRONG&gt;&lt;/P&gt;
  &lt;P&gt;My backend system, S/4HANA, trusts in the same SAP IAS. I can authenticate in SAP IAS and launch Fiori Launchpad (on-premise) and launch SCP application using the same username, due SSO.&lt;/P&gt;
  &lt;P&gt;How can i call the workflow api using SAML authentication mode in an ABAP report and Is it possible to implement principal propagation?&lt;BR /&gt;Note: report will run in background.&lt;/P&gt;
  &lt;P&gt;I know that i can do this using OAuth, but using this authentication mode, i can't implement principal propagation.&lt;/P&gt;
  &lt;P&gt;Cloud Connector does not work in this case because is on-premise pushing data to cloud.&lt;/P&gt;
  &lt;P&gt;Best regards,&lt;/P&gt;
  &lt;P&gt;Guilherme&lt;/P&gt;</description>
      <pubDate>Wed, 15 Apr 2020 03:45:49 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/call-scp-workflow-api-from-abap-program/qaq-p/12189967</guid>
      <dc:creator>former_member639664</dc:creator>
      <dc:date>2020-04-15T03:45:49Z</dc:date>
    </item>
    <item>
      <title>Re: Call SCP Workflow API from ABAP program</title>
      <link>https://community.sap.com/t5/technology-q-a/call-scp-workflow-api-from-abap-program/qaa-p/12189968#M4560047</link>
      <description>&lt;P&gt;Hi Guilherme,&lt;/P&gt;&lt;P&gt;very interesting scenario. Please let us know if you're in the Neo or Cloud Foundry environment.&lt;/P&gt;&lt;P&gt;Would it be an option to send the user a notification in the Cloud Launchpad and the Workflow API is then triggered by the user starting the process?&lt;/P&gt;&lt;P&gt;Best regards&lt;BR /&gt;Gregor&lt;/P&gt;</description>
      <pubDate>Wed, 15 Apr 2020 05:53:40 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/call-scp-workflow-api-from-abap-program/qaa-p/12189968#M4560047</guid>
      <dc:creator>gregorw</dc:creator>
      <dc:date>2020-04-15T05:53:40Z</dc:date>
    </item>
    <item>
      <title>Re: Call SCP Workflow API from ABAP program</title>
      <link>https://community.sap.com/t5/technology-q-a/call-scp-workflow-api-from-abap-program/qaa-p/12189969#M4560048</link>
      <description>&lt;P&gt;Hi Gregor,&lt;/P&gt;&lt;P&gt;Neo environment.&lt;/P&gt;&lt;P&gt;No, it's not an option to send the user a notification in the Cloud Launchpad, but we would like to monitor who is starting the process.&lt;/P&gt;&lt;P&gt;Using OAuth authentication, user oauth_client_MY_ID is the workflow initiator and is the user displayed in the My Inbox application for end users.&lt;/P&gt;&lt;P&gt;&lt;IMG class="migrated-image" src="https://community.sap.com/legacyfs/online/storage/attachments/storage/7/attachments/1801643-untitled1.png" /&gt;&lt;/P&gt;&lt;P&gt;&lt;IMG class="migrated-image" src="https://community.sap.com/legacyfs/online/storage/attachments/storage/7/attachments/1801644-untitled2.png" /&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 15 Apr 2020 14:27:35 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/call-scp-workflow-api-from-abap-program/qaa-p/12189969#M4560048</guid>
      <dc:creator>former_member639664</dc:creator>
      <dc:date>2020-04-15T14:27:35Z</dc:date>
    </item>
    <item>
      <title>Re: Call SCP Workflow API from ABAP program</title>
      <link>https://community.sap.com/t5/technology-q-a/call-scp-workflow-api-from-abap-program/qaa-p/12189970#M4560049</link>
      <description>&lt;P&gt;Hi Guilherme - Did you find an answer for this. Thanks, Manju&lt;/P&gt;</description>
      <pubDate>Fri, 15 May 2020 14:08:42 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/call-scp-workflow-api-from-abap-program/qaa-p/12189970#M4560049</guid>
      <dc:creator>ManjunathGudisi</dc:creator>
      <dc:date>2020-05-15T14:08:42Z</dc:date>
    </item>
    <item>
      <title>Re: Call SCP Workflow API from ABAP program</title>
      <link>https://community.sap.com/t5/technology-q-a/call-scp-workflow-api-from-abap-program/qaa-p/12189971#M4560050</link>
      <description>&lt;P&gt;Unfortunately not.&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
      <pubDate>Sat, 16 May 2020 03:57:30 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/call-scp-workflow-api-from-abap-program/qaa-p/12189971#M4560050</guid>
      <dc:creator>former_member639664</dc:creator>
      <dc:date>2020-05-16T03:57:30Z</dc:date>
    </item>
    <item>
      <title>Re: Call SCP Workflow API from ABAP program</title>
      <link>https://community.sap.com/t5/technology-q-a/call-scp-workflow-api-from-abap-program/qaa-p/12189972#M4560051</link>
      <description>&lt;P&gt;Hi Guilherme,&lt;/P&gt;&lt;P&gt;have you tried using the ABAP OAuth2 Client (CL_OAUTH2_CLIENT) with a SAP Cloud Platform client profile?&lt;/P&gt;&lt;P&gt;It seems to me it supports SAML 2.0 Bearer Assertion which is kind of the connection between the two approaches of authentication.&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Tobias&lt;/P&gt;</description>
      <pubDate>Mon, 18 May 2020 05:43:44 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/call-scp-workflow-api-from-abap-program/qaa-p/12189972#M4560051</guid>
      <dc:creator>tobias_breyer</dc:creator>
      <dc:date>2020-05-18T05:43:44Z</dc:date>
    </item>
    <item>
      <title>Re: Call SCP Workflow API from ABAP program</title>
      <link>https://community.sap.com/t5/technology-q-a/call-scp-workflow-api-from-abap-program/qaa-p/12189973#M4560052</link>
      <description>&lt;P&gt;Have you tried to use the &lt;A href="https://wiki.scn.sap.com/wiki/display/Security/Access+SAP+Hana+Cloud+Platform+using+the+OAuth+2.0+Client+API"&gt;Access SAP Business Technology Platform - Neo Environment using the OAuth 2.0 Client API&lt;/A&gt; description?&lt;/P&gt;</description>
      <pubDate>Fri, 21 Jan 2022 20:03:27 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/call-scp-workflow-api-from-abap-program/qaa-p/12189973#M4560052</guid>
      <dc:creator>gregorw</dc:creator>
      <dc:date>2022-01-21T20:03:27Z</dc:date>
    </item>
    <item>
      <title>Re: Call SCP Workflow API from ABAP program</title>
      <link>https://community.sap.com/t5/technology-q-a/call-scp-workflow-api-from-abap-program/qaa-p/12189974#M4560053</link>
      <description>&lt;P&gt;Do we have any documents for Cloud Foundry ?&lt;/P&gt;</description>
      <pubDate>Wed, 04 May 2022 02:37:34 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/call-scp-workflow-api-from-abap-program/qaa-p/12189974#M4560053</guid>
      <dc:creator>quyen_sap_viet</dc:creator>
      <dc:date>2022-05-04T02:37:34Z</dc:date>
    </item>
  </channel>
</rss>

