<?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: csrf tokens and web files in Talend Studio</title>
    <link>https://community.qlik.com/t5/Talend-Studio/csrf-tokens-and-web-files/m-p/2365895#M129455</link>
    <description>So I worked out what was missing. When downloading the page to extract the token, I needed to also store a cookie. Then when authenticating, I both read and saved that cookie. After authenticating, subsequent tFileFetch components worked by just reading the cookie. No need to reference the token.</description>
    <pubDate>Tue, 19 Dec 2017 13:40:28 GMT</pubDate>
    <dc:creator>cterenzi</dc:creator>
    <dc:date>2017-12-19T13:40:28Z</dc:date>
    <item>
      <title>csrf tokens and web files</title>
      <link>https://community.qlik.com/t5/Talend-Studio/csrf-tokens-and-web-files/m-p/2365894#M129454</link>
      <description>&lt;P&gt;Has anyone had any experience authenticating with a web page that uses csrf tokens?&amp;nbsp; I had a job break after a web site update, and the culprit seems to be these tokens.&amp;nbsp; I managed to parse the web page and extract the token value on the login page, but including that value with my POST request doesn't seem to be working.&lt;/P&gt;</description>
      <pubDate>Wed, 13 Dec 2017 20:12:00 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/csrf-tokens-and-web-files/m-p/2365894#M129454</guid>
      <dc:creator>cterenzi</dc:creator>
      <dc:date>2017-12-13T20:12:00Z</dc:date>
    </item>
    <item>
      <title>Re: csrf tokens and web files</title>
      <link>https://community.qlik.com/t5/Talend-Studio/csrf-tokens-and-web-files/m-p/2365895#M129455</link>
      <description>So I worked out what was missing. When downloading the page to extract the token, I needed to also store a cookie. Then when authenticating, I both read and saved that cookie. After authenticating, subsequent tFileFetch components worked by just reading the cookie. No need to reference the token.</description>
      <pubDate>Tue, 19 Dec 2017 13:40:28 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/csrf-tokens-and-web-files/m-p/2365895#M129455</guid>
      <dc:creator>cterenzi</dc:creator>
      <dc:date>2017-12-19T13:40:28Z</dc:date>
    </item>
  </channel>
</rss>

