<?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: Hiding API Keys in Web AppBuilder Custom Widgets Questions</title>
    <link>https://community.esri.com/t5/web-appbuilder-custom-widgets-questions/hiding-api-keys/m-p/864850#M12238</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P class=""&gt;Hamish,&lt;/P&gt;&lt;P class=""&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P class=""&gt;&amp;nbsp; And JavaScript code or json files you put the API key in can be read. The best you can do is minify/uglify your js code to make less readable.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 26 Sep 2016 00:03:25 GMT</pubDate>
    <dc:creator>RobertScheitlin__GISP</dc:creator>
    <dc:date>2016-09-26T00:03:25Z</dc:date>
    <item>
      <title>Hiding API Keys</title>
      <link>https://community.esri.com/t5/web-appbuilder-custom-widgets-questions/hiding-api-keys/m-p/864849#M12237</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi All&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm currently developing a headless custom JS widget for WAB that makes use of a few third party APIs. These require API keys. I was wondering how I should hide these keys so others can't use them. I did a quick google search but would like to hear what GIS developers might suggest&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cheers&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 25 Sep 2016 23:14:53 GMT</pubDate>
      <guid>https://community.esri.com/t5/web-appbuilder-custom-widgets-questions/hiding-api-keys/m-p/864849#M12237</guid>
      <dc:creator>HamishKingsbury2</dc:creator>
      <dc:date>2016-09-25T23:14:53Z</dc:date>
    </item>
    <item>
      <title>Re: Hiding API Keys</title>
      <link>https://community.esri.com/t5/web-appbuilder-custom-widgets-questions/hiding-api-keys/m-p/864850#M12238</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P class=""&gt;Hamish,&lt;/P&gt;&lt;P class=""&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P class=""&gt;&amp;nbsp; And JavaScript code or json files you put the API key in can be read. The best you can do is minify/uglify your js code to make less readable.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 26 Sep 2016 00:03:25 GMT</pubDate>
      <guid>https://community.esri.com/t5/web-appbuilder-custom-widgets-questions/hiding-api-keys/m-p/864850#M12238</guid>
      <dc:creator>RobertScheitlin__GISP</dc:creator>
      <dc:date>2016-09-26T00:03:25Z</dc:date>
    </item>
    <item>
      <title>Re: Hiding API Keys</title>
      <link>https://community.esri.com/t5/web-appbuilder-custom-widgets-questions/hiding-api-keys/m-p/864851#M12239</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;That's one solution and will most likely be my approach. I'll keep looking and see if I can come up with anything more secure&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 26 Sep 2016 00:14:11 GMT</pubDate>
      <guid>https://community.esri.com/t5/web-appbuilder-custom-widgets-questions/hiding-api-keys/m-p/864851#M12239</guid>
      <dc:creator>HamishKingsbury2</dc:creator>
      <dc:date>2016-09-26T00:14:11Z</dc:date>
    </item>
  </channel>
</rss>

