<?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>idea Creating a security layer around the Flex, Javascript, and/or Silverlight Viewers, and allowing end users to configure away in Developers Ideas</title>
    <link>https://community.esri.com/t5/developers-ideas/creating-a-security-layer-around-the-flex/idi-p/930259</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;One day our end user came to us and said, "we found this cool new tool that ESRI provides called a Flex Viewer&lt;BR /&gt;that allows us to create our own web maps without needing you pesky IT people." Soon after they returned to&lt;BR /&gt;us and said, "we created this map for someone, but they're telling us that not everyone should be allowed&lt;BR /&gt;to see it. Maybe we do need you after all."&lt;/P&gt;

&lt;P&gt;So the issue is, how do we allow our customers to continue to create and edit their own maps, and secure&lt;BR /&gt;the maps so that only certain people could see them. Other considerations were, retaining copies of old&lt;BR /&gt;configuration files for back up and recovery, and using a single library of widgets for all viewers.&lt;/P&gt;

&lt;P&gt;Our solution was to wrap a Flex Viewer in a J2EE container, store all the configuration files in a&lt;BR /&gt;database, and create a front end for our customers to edit the configuration files. You then have to&lt;BR /&gt;get access to any configuration file you want to edit or view as a map.&lt;/P&gt;

&lt;P&gt;This has been a great success at our company. We currently have 15 flex viewers in production, and&lt;BR /&gt;almost 40 in the development phases. All run off the same web server. All use the same library of&lt;BR /&gt;available widgets. The viewer in use is the standard Flex Viewer from ESRI. We have upgraded it twice&lt;BR /&gt;from 2.3 to 2.4 to 2.5&lt;/P&gt;

&lt;!-- content transformation source ID: 08730000000btOG --&gt;

&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 11 Jan 2012 20:36:04 GMT</pubDate>
    <dc:creator>MattHensley</dc:creator>
    <dc:date>2012-01-11T20:36:04Z</dc:date>
    <item>
      <title>Creating a security layer around the Flex, Javascript, and/or Silverlight Viewers, and allowing end users to configure away</title>
      <link>https://community.esri.com/t5/developers-ideas/creating-a-security-layer-around-the-flex/idi-p/930259</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;One day our end user came to us and said, "we found this cool new tool that ESRI provides called a Flex Viewer&lt;BR /&gt;that allows us to create our own web maps without needing you pesky IT people." Soon after they returned to&lt;BR /&gt;us and said, "we created this map for someone, but they're telling us that not everyone should be allowed&lt;BR /&gt;to see it. Maybe we do need you after all."&lt;/P&gt;

&lt;P&gt;So the issue is, how do we allow our customers to continue to create and edit their own maps, and secure&lt;BR /&gt;the maps so that only certain people could see them. Other considerations were, retaining copies of old&lt;BR /&gt;configuration files for back up and recovery, and using a single library of widgets for all viewers.&lt;/P&gt;

&lt;P&gt;Our solution was to wrap a Flex Viewer in a J2EE container, store all the configuration files in a&lt;BR /&gt;database, and create a front end for our customers to edit the configuration files. You then have to&lt;BR /&gt;get access to any configuration file you want to edit or view as a map.&lt;/P&gt;

&lt;P&gt;This has been a great success at our company. We currently have 15 flex viewers in production, and&lt;BR /&gt;almost 40 in the development phases. All run off the same web server. All use the same library of&lt;BR /&gt;available widgets. The viewer in use is the standard Flex Viewer from ESRI. We have upgraded it twice&lt;BR /&gt;from 2.3 to 2.4 to 2.5&lt;/P&gt;

&lt;!-- content transformation source ID: 08730000000btOG --&gt;

&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 11 Jan 2012 20:36:04 GMT</pubDate>
      <guid>https://community.esri.com/t5/developers-ideas/creating-a-security-layer-around-the-flex/idi-p/930259</guid>
      <dc:creator>MattHensley</dc:creator>
      <dc:date>2012-01-11T20:36:04Z</dc:date>
    </item>
    <item>
      <title>Re: Creating a security layer around the Flex, Javascript, and/or Silverlight Viewers, and allowing end users to configure away</title>
      <link>https://community.esri.com/t5/developers-ideas/creating-a-security-layer-around-the-flex/idc-p/930260#M271</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;This is a good idea

&lt;!-- content transformation source ID: 00a3000000DMJEK --&gt;

&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 13 Jan 2012 16:28:20 GMT</pubDate>
      <guid>https://community.esri.com/t5/developers-ideas/creating-a-security-layer-around-the-flex/idc-p/930260#M271</guid>
      <dc:creator>SenthilTt</dc:creator>
      <dc:date>2012-01-13T16:28:20Z</dc:date>
    </item>
    <item>
      <title>Re: Creating a security layer around the Flex, Javascript, and/or Silverlight Viewers, and allowing end users to configure away</title>
      <link>https://community.esri.com/t5/developers-ideas/creating-a-security-layer-around-the-flex/idc-p/930261#M272</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;This idea was submitted some time ago, but I would recommend looking into Portal for ArcGIS for your security concerns and data/change management of your web applications:&amp;nbsp;&lt;A href="http://server.arcgis.com/en/portal/" target="_blank"&gt;http://server.arcgis.com/en/portal/&lt;/A&gt;

&lt;!-- content transformation source ID: 00aE000000FIiWD --&gt;

&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 18 Nov 2015 22:45:59 GMT</pubDate>
      <guid>https://community.esri.com/t5/developers-ideas/creating-a-security-layer-around-the-flex/idc-p/930261#M272</guid>
      <dc:creator>ScottPrindle</dc:creator>
      <dc:date>2015-11-18T22:45:59Z</dc:date>
    </item>
  </channel>
</rss>

