<?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 security tokens in ArcGIS API for Flex Questions</title>
    <link>https://community.esri.com/t5/arcgis-api-for-flex-questions/security-tokens/m-p/400097#M9343</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;i'm generating long-term tokens serverside (using referrer as client) &amp;amp; storing them. seems to work ok using http REST calls outside of flex (in coldfusion). however i'm getting invalid token errors when i try the same token inside our flex app (actually not getting anything for the dynamic layers, no display no errors but if if force a query task, then i can see the bad token errors). &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;we can't use the identity manager as access to the app, map services, etc is already controlled via a complex authentication system.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;do we need to generate the tokens from within flex for this work (seen a few posts alluding to this)?&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;thanks.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;ps: the API docs have an example that uses the token on both the layer URL &amp;amp; as a parameter. pretty sure that's a typo.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 22 Feb 2013 14:34:37 GMT</pubDate>
    <dc:creator>PaulHastings1</dc:creator>
    <dc:date>2013-02-22T14:34:37Z</dc:date>
    <item>
      <title>security tokens</title>
      <link>https://community.esri.com/t5/arcgis-api-for-flex-questions/security-tokens/m-p/400097#M9343</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;i'm generating long-term tokens serverside (using referrer as client) &amp;amp; storing them. seems to work ok using http REST calls outside of flex (in coldfusion). however i'm getting invalid token errors when i try the same token inside our flex app (actually not getting anything for the dynamic layers, no display no errors but if if force a query task, then i can see the bad token errors). &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;we can't use the identity manager as access to the app, map services, etc is already controlled via a complex authentication system.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;do we need to generate the tokens from within flex for this work (seen a few posts alluding to this)?&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;thanks.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;ps: the API docs have an example that uses the token on both the layer URL &amp;amp; as a parameter. pretty sure that's a typo.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 22 Feb 2013 14:34:37 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-api-for-flex-questions/security-tokens/m-p/400097#M9343</guid>
      <dc:creator>PaulHastings1</dc:creator>
      <dc:date>2013-02-22T14:34:37Z</dc:date>
    </item>
    <item>
      <title>Re: security tokens</title>
      <link>https://community.esri.com/t5/arcgis-api-for-flex-questions/security-tokens/m-p/400098#M9344</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;looks like the referrer as client won't work from flex. no matter how i generate the token outside of flex or what i use as referrer, client referrer fails. IP (either flavor) seems to work ok.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;if that's really the case, perhaps that should be documented some place?&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 24 Feb 2013 02:47:37 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-api-for-flex-questions/security-tokens/m-p/400098#M9344</guid>
      <dc:creator>PaulHastings1</dc:creator>
      <dc:date>2013-02-24T02:47:37Z</dc:date>
    </item>
  </channel>
</rss>

