<?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: Qlik Sense e twitter in Brasil</title>
    <link>https://community.qlik.com/t5/Brasil/Qlik-Sense-e-twitter/m-p/1422849#M52028</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Lendo aqui : &lt;A href="https://dev.twitter.com/oauth/overview/authorizing-requests" title="https://dev.twitter.com/oauth/overview/authorizing-requests"&gt;https://dev.twitter.com/oauth/overview/authorizing-requests&lt;/A&gt;&lt;/P&gt;&lt;P&gt;No exemplo a autorização parece ser passada no "Body"&lt;/P&gt;&lt;P&gt;POST /1.1/statuses/update.json?include_entities=true HTTP/1.1&lt;/P&gt;&lt;P&gt;Accept: */*&lt;/P&gt;&lt;P&gt;Connection: close&lt;/P&gt;&lt;P&gt;User-Agent: OAuth gem v0.4.4&lt;/P&gt;&lt;P&gt;Content-Type: application/x-www-form-urlencoded&lt;/P&gt;&lt;P&gt;Authorization:&lt;/P&gt;&lt;P&gt;&amp;nbsp; OAuth oauth_consumer_key="xvz1evFS4wEEPTGEFPHBog",&lt;/P&gt;&lt;P&gt;&amp;nbsp; oauth_nonce="kYjzVBB8Y0ZFabxSWbWovY3uYSQ2pTgmZeNu2VS4cg",&lt;/P&gt;&lt;P&gt;&amp;nbsp; oauth_signature="tnnArxj06cWHq44gCs1OSKk%2FjLY%3D",&lt;/P&gt;&lt;P&gt;&amp;nbsp; oauth_signature_method="HMAC-SHA1",&lt;/P&gt;&lt;P&gt;&amp;nbsp; oauth_timestamp="1318622958",&lt;/P&gt;&lt;P&gt;&amp;nbsp; oauth_token="370773112-GmHxMAgYyLbNEtIKZeRNFsMKPR9EyMZeS9weJAEb",&lt;/P&gt;&lt;P&gt;&amp;nbsp; oauth_version="1.0"&lt;/P&gt;&lt;P&gt;Content-Length: 76&lt;/P&gt;&lt;P&gt;Host: api.twitter.com&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 18 Aug 2017 14:55:22 GMT</pubDate>
    <dc:creator>Clever_Anjos</dc:creator>
    <dc:date>2017-08-18T14:55:22Z</dc:date>
    <item>
      <title>Qlik Sense e twitter</title>
      <link>https://community.qlik.com/t5/Brasil/Qlik-Sense-e-twitter/m-p/1422845#M52024</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Boa noite senhores do Qlik,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Estou tentando conectar o qlik sense ao twitter via rest, porem ao criar a conexão, ocorre uma falha na autenticação.&lt;/P&gt;&lt;P&gt;cod 215 - bad authentcationdata.&lt;/P&gt;&lt;P&gt;Estou começando a usar o sense agora, algum de vocês ja enfrentou esse problema.&lt;/P&gt;&lt;P&gt;Obs: gero os dados para a conexão no &lt;A href="https://apigee.com/console/twitter" title="https://apigee.com/console/twitter"&gt;apigee.com/console/twitter&lt;/A&gt; e la funciona a requisição normalmente.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Agradeço.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 18 Aug 2017 00:56:59 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Brasil/Qlik-Sense-e-twitter/m-p/1422845#M52024</guid>
      <dc:creator />
      <dc:date>2017-08-18T00:56:59Z</dc:date>
    </item>
    <item>
      <title>Re: Qlik Sense e twitter</title>
      <link>https://community.qlik.com/t5/Brasil/Qlik-Sense-e-twitter/m-p/1422846#M52025</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Como está passando a autenticação?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 18 Aug 2017 11:52:34 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Brasil/Qlik-Sense-e-twitter/m-p/1422846#M52025</guid>
      <dc:creator>Clever_Anjos</dc:creator>
      <dc:date>2017-08-18T11:52:34Z</dc:date>
    </item>
    <item>
      <title>Re: Qlik Sense e twitter</title>
      <link>https://community.qlik.com/t5/Brasil/Qlik-Sense-e-twitter/m-p/1422847#M52026</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Clever,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Como os dados estão no apigee!&lt;/P&gt;&lt;P&gt;Segue um print.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;IMG class="jive-image" src="https://raw.githubusercontent.com/marosvongrej/Twitter-User-Analyser/master/QSSET2.png" /&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 18 Aug 2017 14:38:11 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Brasil/Qlik-Sense-e-twitter/m-p/1422847#M52026</guid>
      <dc:creator />
      <dc:date>2017-08-18T14:38:11Z</dc:date>
    </item>
    <item>
      <title>Re: Qlik Sense e twitter</title>
      <link>https://community.qlik.com/t5/Brasil/Qlik-Sense-e-twitter/m-p/1422848#M52027</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;O jeito certo é passar no Query headers mesmo? &lt;/P&gt;&lt;P&gt;Já tentou passar no "Body"?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 18 Aug 2017 14:54:29 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Brasil/Qlik-Sense-e-twitter/m-p/1422848#M52027</guid>
      <dc:creator>Clever_Anjos</dc:creator>
      <dc:date>2017-08-18T14:54:29Z</dc:date>
    </item>
    <item>
      <title>Re: Qlik Sense e twitter</title>
      <link>https://community.qlik.com/t5/Brasil/Qlik-Sense-e-twitter/m-p/1422849#M52028</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Lendo aqui : &lt;A href="https://dev.twitter.com/oauth/overview/authorizing-requests" title="https://dev.twitter.com/oauth/overview/authorizing-requests"&gt;https://dev.twitter.com/oauth/overview/authorizing-requests&lt;/A&gt;&lt;/P&gt;&lt;P&gt;No exemplo a autorização parece ser passada no "Body"&lt;/P&gt;&lt;P&gt;POST /1.1/statuses/update.json?include_entities=true HTTP/1.1&lt;/P&gt;&lt;P&gt;Accept: */*&lt;/P&gt;&lt;P&gt;Connection: close&lt;/P&gt;&lt;P&gt;User-Agent: OAuth gem v0.4.4&lt;/P&gt;&lt;P&gt;Content-Type: application/x-www-form-urlencoded&lt;/P&gt;&lt;P&gt;Authorization:&lt;/P&gt;&lt;P&gt;&amp;nbsp; OAuth oauth_consumer_key="xvz1evFS4wEEPTGEFPHBog",&lt;/P&gt;&lt;P&gt;&amp;nbsp; oauth_nonce="kYjzVBB8Y0ZFabxSWbWovY3uYSQ2pTgmZeNu2VS4cg",&lt;/P&gt;&lt;P&gt;&amp;nbsp; oauth_signature="tnnArxj06cWHq44gCs1OSKk%2FjLY%3D",&lt;/P&gt;&lt;P&gt;&amp;nbsp; oauth_signature_method="HMAC-SHA1",&lt;/P&gt;&lt;P&gt;&amp;nbsp; oauth_timestamp="1318622958",&lt;/P&gt;&lt;P&gt;&amp;nbsp; oauth_token="370773112-GmHxMAgYyLbNEtIKZeRNFsMKPR9EyMZeS9weJAEb",&lt;/P&gt;&lt;P&gt;&amp;nbsp; oauth_version="1.0"&lt;/P&gt;&lt;P&gt;Content-Length: 76&lt;/P&gt;&lt;P&gt;Host: api.twitter.com&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 18 Aug 2017 14:55:22 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Brasil/Qlik-Sense-e-twitter/m-p/1422849#M52028</guid>
      <dc:creator>Clever_Anjos</dc:creator>
      <dc:date>2017-08-18T14:55:22Z</dc:date>
    </item>
    <item>
      <title>Re: Qlik Sense e twitter</title>
      <link>https://community.qlik.com/t5/Brasil/Qlik-Sense-e-twitter/m-p/1422850#M52029</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Marciel, &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Dá uma olhada nesse post:&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.qlik.com/thread/278153"&gt;REST connector Qliksense error:    code 215 message "Bad Authentication data."&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Nele você encontrará um link para um vídeo tutorial. Veja, estou apenas recomendando este vídeo para que você possa verificar se em alguma etapa de config. houve algum erro.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Nesse outro post, o problema foi solucionado e nele há também um manual para config do conector REST.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.qlik.com/thread/198343"&gt;REST API - Help connecting to Twitter please?&lt;/A&gt;‌&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Abraços e sucesso!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 21 Dec 2017 21:52:45 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Brasil/Qlik-Sense-e-twitter/m-p/1422850#M52029</guid>
      <dc:creator>Thiago_Justen_</dc:creator>
      <dc:date>2017-12-21T21:52:45Z</dc:date>
    </item>
  </channel>
</rss>

