<?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 Encrypting Password in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/encrypting-password/m-p/3836790#M922635</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We use the FM DB_CRYPTO_PASSWORD to encrpyt our password. The FM encrypt a word different on a non-UNICODE-System and an UNICODE-System.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;At the moment we haven't an UNICODE-System. If we migrate our system into an UNICODE-System, is it possible to "translate" our "old" passwords stored in a data base, so that the passwords are also valid on the UNICODE-System?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best regards,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Marion Kühl&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 14 May 2008 14:14:07 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2008-05-14T14:14:07Z</dc:date>
    <item>
      <title>Encrypting Password</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/encrypting-password/m-p/3836790#M922635</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We use the FM DB_CRYPTO_PASSWORD to encrpyt our password. The FM encrypt a word different on a non-UNICODE-System and an UNICODE-System.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;At the moment we haven't an UNICODE-System. If we migrate our system into an UNICODE-System, is it possible to "translate" our "old" passwords stored in a data base, so that the passwords are also valid on the UNICODE-System?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best regards,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Marion Kühl&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 14 May 2008 14:14:07 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/encrypting-password/m-p/3836790#M922635</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-05-14T14:14:07Z</dc:date>
    </item>
    <item>
      <title>Re: Encrypting Password</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/encrypting-password/m-p/3836791#M922636</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;If the table is SAP standard then SAP take cares of translation of database into UNICODE but if it is in the Z name space then keep the program using this table unicode disabled so that it would work in the same was as it used to.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;FY&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 14 May 2008 14:16:47 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/encrypting-password/m-p/3836791#M922636</guid>
      <dc:creator>former_member226999</dc:creator>
      <dc:date>2008-05-14T14:16:47Z</dc:date>
    </item>
    <item>
      <title>Re: Encrypting Password</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/encrypting-password/m-p/3836792#M922637</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;this doesn't solve the problem. Once again: We encrypt the password with the FM DB_CRYPTO_PASSWORD  and stored it in a data base table (our name space, not a SAP table). Then we migrated our SAP-System into a UNICODE-System, so that we can't keep any program (or function group) unicode disabled. After that the password will be enter the next time: We will encrypt the password (again with the FM DB_CRYPTO_PASSWORD) and compare with the encrypted password stored in the table. At the moment the result is different (on our test system).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best regards,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Marion&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 14 May 2008 15:38:50 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/encrypting-password/m-p/3836792#M922637</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-05-14T15:38:50Z</dc:date>
    </item>
  </channel>
</rss>

