<?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: Decrypt using Triple-DES algorithm in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/decrypt-using-triple-des-algorithm/m-p/1723024#M315416</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi folks,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For your information, I would like to tell you that the problem of my customer was fixed without SSF functions &lt;SPAN __jive_emoticon_name="happy"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I used the advantage of XI that it has and develop an interface between SAP ERP and XI via ABAP proxy. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The scenario is: on se38 runs a report that calls an outbound synchronous method of ABAP proxy. The encrypted fields are sent to XI, in your turn; XI sends the message to the inbound interface (also ABAP proxy). This inbound interface has a simple role of send the message back as it has (ex. move input to output.). Between interface, I develop a java mapping and inside of them, I call a crypto class with TDES algorithm and with the own key.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It works fine and the customer is satisfied &lt;SPAN __jive_emoticon_name="happy"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for all,&lt;/P&gt;&lt;P&gt;Ricardo Pereira.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 10 Nov 2006 12:28:13 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2006-11-10T12:28:13Z</dc:date>
    <item>
      <title>Decrypt using Triple-DES algorithm</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/decrypt-using-triple-des-algorithm/m-p/1723021#M315413</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi folks,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The scenario is: My client receives messages in XML format; some of the fields are encrypted with algorithm Triple-DES. This information is stored into a Z table of a SAP ERP 2005. The idea is develop an ABAP report that reads this table and decrypt the encrypted fields. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I already read all most information about Triple-DES on SAP help. The SSF (Secure Store and Forward) supports this kind algorithm. But a contradiction happens, the Triple-DES is a symmetric algorithm (the same key is used to encrypt and decrypt data), however, the infrastructure mentioned on a SAP Help shows only the public key technology (asymmetric cryptography). Also SFF functions have parameters to fill, like recipient information, etc&amp;#133; it means that those functions are to be used with public key algorithm? &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As I have all the encrypted data into the tables and also the private key on my own, I think that I only need to call a function to decrypt data. So, it means only a SSF_DEVELOPE function is necessary? &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have more questions:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Where is the safe place to save the private key? (Transaction)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Which extra configurations I need to do to start my ABAP report?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Which functions of a SSFG function group I need to use? Like I said before I think that I only need to decrypt the encrypted data, so it means only a SSF_DEVELOPE function is necessary?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks a lot for your help.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Ricardo.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 02 Nov 2006 16:25:13 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/decrypt-using-triple-des-algorithm/m-p/1723021#M315413</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-11-02T16:25:13Z</dc:date>
    </item>
    <item>
      <title>Re: Decrypt using Triple-DES algorithm</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/decrypt-using-triple-des-algorithm/m-p/1723022#M315414</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Ricardo,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;the idea behind SSF is having a strong and save encryption (and signature) of data. To ensure this, SSF uses hybride encryption technology. The message itself is encrypted using a symmetric algorithm. For security reasons the key is randomly generated for each message, so there is no need to secure distribute and store a symmetric key. The key itself is then encrypted using a public key algorithm and attached to the encrypted message which is formatted in a certain way (PKCS#7, S/MIME, etc.)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So I think, you will not be successfull decrypting your ciphertext with the SSF library.....&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 09 Nov 2006 08:21:00 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/decrypt-using-triple-des-algorithm/m-p/1723022#M315414</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-11-09T08:21:00Z</dc:date>
    </item>
    <item>
      <title>Re: Decrypt using Triple-DES algorithm</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/decrypt-using-triple-des-algorithm/m-p/1723023#M315415</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Well, when there is a message recipient then there's also a message sender. In your approach both have to share a symmetric key - this approach will not scale (without severe security impact). Furthermore the 3DES key seems to be static - and needs to be exchanged prior usage ("somehow" offline).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As Michael has pointed out, there is a much better (hybride) approach. In that case the recipient has to know the public key of the sender - and vice versa, the sender has to know the public key(s) of the (intended) recipient(s). That implies the requirement for a PKI (Public Key Infrastructure). This approach might look more complicated at first glimpse but has multiple advantages (regarding scalability and data security, including also aspects such as non-repudiation which cannot be achieved by using shared symmetric keys).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Especially for XML documents there are standards called "XML encryption" and "XML signature". &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards, Wolfgang&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 09 Nov 2006 11:02:10 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/decrypt-using-triple-des-algorithm/m-p/1723023#M315415</guid>
      <dc:creator>Wolfgang_Janzen</dc:creator>
      <dc:date>2006-11-09T11:02:10Z</dc:date>
    </item>
    <item>
      <title>Re: Decrypt using Triple-DES algorithm</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/decrypt-using-triple-des-algorithm/m-p/1723024#M315416</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi folks,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For your information, I would like to tell you that the problem of my customer was fixed without SSF functions &lt;SPAN __jive_emoticon_name="happy"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I used the advantage of XI that it has and develop an interface between SAP ERP and XI via ABAP proxy. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The scenario is: on se38 runs a report that calls an outbound synchronous method of ABAP proxy. The encrypted fields are sent to XI, in your turn; XI sends the message to the inbound interface (also ABAP proxy). This inbound interface has a simple role of send the message back as it has (ex. move input to output.). Between interface, I develop a java mapping and inside of them, I call a crypto class with TDES algorithm and with the own key.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It works fine and the customer is satisfied &lt;SPAN __jive_emoticon_name="happy"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for all,&lt;/P&gt;&lt;P&gt;Ricardo Pereira.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 10 Nov 2006 12:28:13 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/decrypt-using-triple-des-algorithm/m-p/1723024#M315416</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-11-10T12:28:13Z</dc:date>
    </item>
    <item>
      <title>Re: Decrypt using Triple-DES algorithm</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/decrypt-using-triple-des-algorithm/m-p/1723025#M315417</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Well, that's one possible approach.&lt;/P&gt;&lt;P&gt;Another one would be: write your own "decryption service" (either implemented as web service in Java or as RFC server in C) and call it from your ABAP application.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As stated above: there is no ABAP function module providing (plain) decryption functions. So, you have to find alternative solutions - as you did.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Still remains valid:&lt;/P&gt;&lt;P&gt;such symmetric algorithms (with static stored keys) are not a good solution.&lt;/P&gt;&lt;P&gt;That's why you'll not find any offerings in the standard (ABAP). For J2EE things are different.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cheers, Wolfgang&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 10 Nov 2006 12:38:04 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/decrypt-using-triple-des-algorithm/m-p/1723025#M315417</guid>
      <dc:creator>Wolfgang_Janzen</dc:creator>
      <dc:date>2006-11-10T12:38:04Z</dc:date>
    </item>
    <item>
      <title>Re: Decrypt using Triple-DES algorithm</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/decrypt-using-triple-des-algorithm/m-p/1723026#M315418</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;PRE&gt;&lt;CODE&gt;
&lt;P&gt;Wolfgang Janzen wrote:&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;As stated above: there is no ABAP function module providing (plain) decryption functions.&lt;/P&gt;
&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hello Wolfgang (and others), is this statement of yours still true, now as of the year 2016?&lt;/P&gt;&lt;P&gt;So in other words: Can one use SAP SSF somehow to decrypt AES- (or alike) encrypted data?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cheers!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 20 Jan 2016 08:34:17 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/decrypt-using-triple-des-algorithm/m-p/1723026#M315418</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2016-01-20T08:34:17Z</dc:date>
    </item>
  </channel>
</rss>

