<?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: User and password encryption in odbc string in QlikView</title>
    <link>https://community.qlik.com/t5/QlikView/User-and-password-encryption-in-odbc-string/m-p/438982#M699927</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Depends on what you mean... &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The XUser and XPassword parameters in the connection string are &lt;EM&gt;&lt;STRONG&gt;not &lt;/STRONG&gt;&lt;/EM&gt;encrypted. They are merely scrambled so that it is not possible to read the password when you look at someone else's screen. Obuscation - not encryption.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The credentials are passed to the ODBC driver (on the same computer) in clear text. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The ODBC driver in turn, sends the credentials to the RDBM server. This step can often be properly encrypted, but this is done by the ODBC driver, not by QlikView. So, look in the settings of your ODBC driver or OLEDB provider.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;HIC&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 16 Nov 2012 10:19:42 GMT</pubDate>
    <dc:creator>hic</dc:creator>
    <dc:date>2012-11-16T10:19:42Z</dc:date>
    <item>
      <title>User and password encryption in odbc string</title>
      <link>https://community.qlik.com/t5/QlikView/User-and-password-encryption-in-odbc-string/m-p/438981#M699926</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;Does anybody know wich type of encryption algorithm is used by Qlikview in ODBC strings? &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I was reading the reference manual but I didn't found anything.&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;Leo.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 15 Nov 2012 18:27:18 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/User-and-password-encryption-in-odbc-string/m-p/438981#M699926</guid>
      <dc:creator>leonardo_raed</dc:creator>
      <dc:date>2012-11-15T18:27:18Z</dc:date>
    </item>
    <item>
      <title>Re: User and password encryption in odbc string</title>
      <link>https://community.qlik.com/t5/QlikView/User-and-password-encryption-in-odbc-string/m-p/438982#M699927</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Depends on what you mean... &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The XUser and XPassword parameters in the connection string are &lt;EM&gt;&lt;STRONG&gt;not &lt;/STRONG&gt;&lt;/EM&gt;encrypted. They are merely scrambled so that it is not possible to read the password when you look at someone else's screen. Obuscation - not encryption.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The credentials are passed to the ODBC driver (on the same computer) in clear text. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The ODBC driver in turn, sends the credentials to the RDBM server. This step can often be properly encrypted, but this is done by the ODBC driver, not by QlikView. So, look in the settings of your ODBC driver or OLEDB provider.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;HIC&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 16 Nov 2012 10:19:42 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/User-and-password-encryption-in-odbc-string/m-p/438982#M699927</guid>
      <dc:creator>hic</dc:creator>
      <dc:date>2012-11-16T10:19:42Z</dc:date>
    </item>
    <item>
      <title>Re: User and password encryption in odbc string</title>
      <link>https://community.qlik.com/t5/QlikView/User-and-password-encryption-in-odbc-string/m-p/438983#M699928</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;SPAN style="font-family: calibri,verdana,arial,sans-serif;"&gt;Good question Leonardo. I did some research on this area and found out that QlikView ODBC connection strings are stored in &lt;SPAN style="color: #800000;"&gt;&lt;STRONG&gt;Base64 &lt;/STRONG&gt;&lt;/SPAN&gt;Scrambling method. As suggested by HIC, you can control ODBC connection string encryption outside QlikView. And you have one more option of using VBScript with &lt;A href="http://www.chilkatsoft.com/refdoc/xChilkatCrypt2Ref.html"&gt;ChilkatCrypt2&lt;/A&gt; encryption component. I have not implemented it but this should work. &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: calibri,verdana,arial,sans-serif;"&gt;HIC - Any plans in future versions to add the encryption? Not just ODBC connection string but I'm also concerned about Hidden Script Password...&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: calibri,verdana,arial,sans-serif;"&gt;Thanks in advance.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: calibri,verdana,arial,sans-serif;"&gt;Cheers,&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: calibri,verdana,arial,sans-serif;"&gt;DV&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://QlikShare.com"&gt;&lt;BR /&gt;&lt;/A&gt;&lt;A href="http://QlikShare.com"&gt;&lt;SPAN style="font-family: calibri,verdana,arial,sans-serif;"&gt;www.QlikShare.com&lt;/SPAN&gt;&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 24 Nov 2012 23:45:20 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/User-and-password-encryption-in-odbc-string/m-p/438983#M699928</guid>
      <dc:creator>IAMDV</dc:creator>
      <dc:date>2012-11-24T23:45:20Z</dc:date>
    </item>
  </channel>
</rss>

