<?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: SAP PI HTTP POST dynamic basic authentication string in Technology Q&amp;A</title>
    <link>https://community.sap.com/t5/technology-q-a/sap-pi-http-post-dynamic-basic-authentication-string/qaa-p/420658#M53103</link>
    <description>&lt;P&gt;Hi &lt;A href="https://answers.sap.com/users/166165/sapbinarykey.html"&gt;sapbinary key&lt;/A&gt;&lt;/P&gt;
  &lt;P&gt;hi Manoj&lt;/P&gt;
  &lt;P&gt;thanks for your responses.&lt;/P&gt;
  &lt;P&gt;I set up an test scenario SOAP -&amp;gt; PI -&amp;gt; (TCP Tracing) -&amp;gt; REST and tried to set HTTP header parameter via ASMA.&lt;/P&gt;
  &lt;P&gt;It looks promising, the HTTP parameters are visible in the trace. Hopefully the receiver system is able to recognize the parameter correctly. the actual receiver do not expect any authentication.&lt;/P&gt;
  &lt;P&gt;I try to enhance my test scenario and use an REST receiver expecting basic authentication have an end-to-end test.&lt;/P&gt;
  &lt;P&gt;I will come back a let you know the result.&lt;/P&gt;
  &lt;P&gt;regarding point 2: my operation is POST.&lt;/P&gt;
  &lt;P&gt;once again thanks for your support.&lt;/P&gt;
  &lt;P&gt;best regards&lt;/P&gt;
  &lt;P&gt;Jochen&lt;/P&gt;</description>
    <pubDate>Wed, 19 Jul 2017 19:49:33 GMT</pubDate>
    <dc:creator>Jochen_Gugel</dc:creator>
    <dc:date>2017-07-19T19:49:33Z</dc:date>
    <item>
      <title>SAP PI HTTP POST dynamic basic authentication string</title>
      <link>https://community.sap.com/t5/technology-q-a/sap-pi-http-post-dynamic-basic-authentication-string/qaq-p/420655</link>
      <description>&lt;P&gt;Dear guys&lt;/P&gt;
  &lt;P&gt;I am facing an integration challenge with specific/enhanced security requirements.&lt;/P&gt;
  &lt;P&gt;There should be an async interface to transfer document from internal system to external webservice via SAP PI java only. &lt;/P&gt;
  &lt;UL&gt; 
   &lt;LI&gt;Sender will be REST&lt;/LI&gt; 
   &lt;LI&gt;receiver also REST (either JSON or XML message as https POST)&lt;/LI&gt; 
  &lt;/UL&gt;
  &lt;P&gt;For security reasons the receiver expects basic authentication, but the authentication string should be dynamic consisting of :&lt;/P&gt;
  &lt;UL&gt; 
   &lt;LI&gt;username (fix)&lt;/LI&gt; 
   &lt;LI&gt;public key (dynamic per Call)&lt;/LI&gt; 
   &lt;LI&gt;encrypted password (dynamic as encrypted by dynamic key)&lt;/LI&gt; 
  &lt;/UL&gt;
  &lt;P&gt;the document should be tranfered directly as base64 string and not be included in JSON or XML structure.&lt;/P&gt;
  &lt;P&gt;Following two main questions arises:&lt;/P&gt;
  &lt;OL&gt; 
   &lt;LI&gt;Is there an possibility to dynamically set basic authentication string in HTTP header? I know it is not possible in SOAP Receiver via ASMA. Maybe there are other ways to set this value dynamically during runtime&lt;/LI&gt; 
   &lt;LI&gt;Does REST or SOAP in plain mode support direct transmitting of base64 string or is structure mandatory e.g. XML with single field. This should be a minor issue.&lt;/LI&gt; 
  &lt;/OL&gt;
  &lt;P&gt;Any Idea how to solve part 1 dynamic basic authentication?&lt;/P&gt;
  &lt;P&gt;Any thoughts or idea appreciated.&lt;/P&gt;
  &lt;P&gt;Best regards&lt;/P&gt;
  &lt;P&gt;Jochen&lt;/P&gt;</description>
      <pubDate>Wed, 19 Jul 2017 09:07:48 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/sap-pi-http-post-dynamic-basic-authentication-string/qaq-p/420655</guid>
      <dc:creator>Jochen_Gugel</dc:creator>
      <dc:date>2017-07-19T09:07:48Z</dc:date>
    </item>
    <item>
      <title>Re: SAP PI HTTP POST dynamic basic authentication string</title>
      <link>https://community.sap.com/t5/technology-q-a/sap-pi-http-post-dynamic-basic-authentication-string/qaa-p/420656#M53101</link>
      <description>&lt;P&gt;point 1 is possible. &lt;/P&gt;
  &lt;P&gt;&lt;A href="https://answers.sap.com/questions/84202/how-configure-dynamic-http-header-in-rest-receiver.html" target="test_blank"&gt;https://answers.sap.com/questions/84202/how-configure-dynamic-http-header-in-rest-receiver.html&lt;/A&gt;&lt;/P&gt;
  &lt;P&gt;you can construct the key UDF or java mapping and put it in dynamic configuration. dynamic configuration variable can be used in Http header of rest receiver channel&lt;/P&gt;
  &lt;P&gt;point 2&lt;/P&gt;
  &lt;P&gt;what is the operation of the service? GET,PUT,POST,etc..&lt;/P&gt;</description>
      <pubDate>Wed, 19 Jul 2017 13:25:35 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/sap-pi-http-post-dynamic-basic-authentication-string/qaa-p/420656#M53101</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2017-07-19T13:25:35Z</dc:date>
    </item>
    <item>
      <title>Re: SAP PI HTTP POST dynamic basic authentication string</title>
      <link>https://community.sap.com/t5/technology-q-a/sap-pi-http-post-dynamic-basic-authentication-string/qaa-p/420657#M53102</link>
      <description>&lt;P&gt;Hi Jochen,&lt;/P&gt;
  &lt;P&gt;1.I don't think this is possible as basic authentication is static in REST channel and there are no Dynamic Configuration variable available for these attributes .&lt;/P&gt;
  &lt;P&gt;2.When you say direct transmitting you mean without any soap envelope or any structure ? just the main output paylaod should have base64 content. &lt;/P&gt;
  &lt;P&gt;Br,&lt;/P&gt;
  &lt;P&gt;Manoj&lt;/P&gt;</description>
      <pubDate>Wed, 19 Jul 2017 14:09:59 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/sap-pi-http-post-dynamic-basic-authentication-string/qaa-p/420657#M53102</guid>
      <dc:creator>manoj_khavatkopp</dc:creator>
      <dc:date>2017-07-19T14:09:59Z</dc:date>
    </item>
    <item>
      <title>Re: SAP PI HTTP POST dynamic basic authentication string</title>
      <link>https://community.sap.com/t5/technology-q-a/sap-pi-http-post-dynamic-basic-authentication-string/qaa-p/420658#M53103</link>
      <description>&lt;P&gt;Hi &lt;A href="https://answers.sap.com/users/166165/sapbinarykey.html"&gt;sapbinary key&lt;/A&gt;&lt;/P&gt;
  &lt;P&gt;hi Manoj&lt;/P&gt;
  &lt;P&gt;thanks for your responses.&lt;/P&gt;
  &lt;P&gt;I set up an test scenario SOAP -&amp;gt; PI -&amp;gt; (TCP Tracing) -&amp;gt; REST and tried to set HTTP header parameter via ASMA.&lt;/P&gt;
  &lt;P&gt;It looks promising, the HTTP parameters are visible in the trace. Hopefully the receiver system is able to recognize the parameter correctly. the actual receiver do not expect any authentication.&lt;/P&gt;
  &lt;P&gt;I try to enhance my test scenario and use an REST receiver expecting basic authentication have an end-to-end test.&lt;/P&gt;
  &lt;P&gt;I will come back a let you know the result.&lt;/P&gt;
  &lt;P&gt;regarding point 2: my operation is POST.&lt;/P&gt;
  &lt;P&gt;once again thanks for your support.&lt;/P&gt;
  &lt;P&gt;best regards&lt;/P&gt;
  &lt;P&gt;Jochen&lt;/P&gt;</description>
      <pubDate>Wed, 19 Jul 2017 19:49:33 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/sap-pi-http-post-dynamic-basic-authentication-string/qaa-p/420658#M53103</guid>
      <dc:creator>Jochen_Gugel</dc:creator>
      <dc:date>2017-07-19T19:49:33Z</dc:date>
    </item>
  </channel>
</rss>

