<?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: Layer based authorization in WebAppBuilder &amp; Portal in Web AppBuilder Custom Widgets Questions</title>
    <link>https://community.esri.com/t5/web-appbuilder-custom-widgets-questions/layer-based-authorization-in-webappbuilder-portal/m-p/778533#M2309</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;As mentioned, the question &amp;nbsp;/ statement is very vague and open to many avenues of security.&lt;/P&gt;&lt;P&gt;Derek has provided a few...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Another&amp;nbsp;way would be to&amp;nbsp;create two services. &amp;nbsp;One would be a mapping service (VIEW of the data) and the other would be the FeatureAccess (Editable featureclasses). Database end would have to enable Update/Select/Delete etc. (whatever you want). &amp;nbsp; &amp;nbsp;You lock down using A.D., the Editing service. (Windows Authentication / Web Tier on ArcGIS Server) in this case, the FeatureAccess service layers. Thus, only users that have editing ability will have those layers show up in the web map and web app and all the remaining users get a 'view' (not editable) of the service layers.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 28 Sep 2016 16:25:07 GMT</pubDate>
    <dc:creator>MichaelRobb</dc:creator>
    <dc:date>2016-09-28T16:25:07Z</dc:date>
    <item>
      <title>Layer based authorization in WebAppBuilder &amp; Portal</title>
      <link>https://community.esri.com/t5/web-appbuilder-custom-widgets-questions/layer-based-authorization-in-webappbuilder-portal/m-p/778531#M2307</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;SPAN style="font-size: 11.0pt;"&gt;Hello there,&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 11.0pt;"&gt;We are using Portal &amp;amp; WebappBuilder. We would like particular users to edit X layer but other users only see it. &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 11.0pt;"&gt;What should we do about layer based authorization?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 27 Sep 2016 10:40:18 GMT</pubDate>
      <guid>https://community.esri.com/t5/web-appbuilder-custom-widgets-questions/layer-based-authorization-in-webappbuilder-portal/m-p/778531#M2307</guid>
      <dc:creator>BugraOtken</dc:creator>
      <dc:date>2016-09-27T10:40:18Z</dc:date>
    </item>
    <item>
      <title>Re: Layer based authorization in WebAppBuilder &amp; Portal</title>
      <link>https://community.esri.com/t5/web-appbuilder-custom-widgets-questions/layer-based-authorization-in-webappbuilder-portal/m-p/778532#M2308</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Bugra,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Your question is a bit too generalized; so I'll mention some resources to get you started. When editing in Web AppBuilder, you are working with feature services.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If the source data for the feature layer you want to edit is a feature service from ArcGIS Server - you can leverage the security model available with feature services such as editor permissions and ownership-based access control.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="link-titled" href="http://server.arcgis.com/en/server/latest/publish-services/windows/feature-service-permissions-and-editor-tracking.htm" title="http://server.arcgis.com/en/server/latest/publish-services/windows/feature-service-permissions-and-editor-tracking.htm"&gt;Feature service permissions and editor tracking—Documentation | ArcGIS for Server&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If the source data for the feature layer is a hosted feature service in Portal for ArcGIS, you can access the item details page and set editing permissions for it.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="link-titled" href="http://server.arcgis.com/en/portal/latest/use/manage-hosted-layers.htm#ESRI_SECTION1_FFEC223155964B2195C03F43BEC4D2B9" title="http://server.arcgis.com/en/portal/latest/use/manage-hosted-layers.htm#ESRI_SECTION1_FFEC223155964B2195C03F43BEC4D2B9"&gt;Manage hosted web layers—Portal for ArcGIS | ArcGIS for Server&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this helps,&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 27 Sep 2016 22:30:39 GMT</pubDate>
      <guid>https://community.esri.com/t5/web-appbuilder-custom-widgets-questions/layer-based-authorization-in-webappbuilder-portal/m-p/778532#M2308</guid>
      <dc:creator>DerekLaw</dc:creator>
      <dc:date>2016-09-27T22:30:39Z</dc:date>
    </item>
    <item>
      <title>Re: Layer based authorization in WebAppBuilder &amp; Portal</title>
      <link>https://community.esri.com/t5/web-appbuilder-custom-widgets-questions/layer-based-authorization-in-webappbuilder-portal/m-p/778533#M2309</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;As mentioned, the question &amp;nbsp;/ statement is very vague and open to many avenues of security.&lt;/P&gt;&lt;P&gt;Derek has provided a few...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Another&amp;nbsp;way would be to&amp;nbsp;create two services. &amp;nbsp;One would be a mapping service (VIEW of the data) and the other would be the FeatureAccess (Editable featureclasses). Database end would have to enable Update/Select/Delete etc. (whatever you want). &amp;nbsp; &amp;nbsp;You lock down using A.D., the Editing service. (Windows Authentication / Web Tier on ArcGIS Server) in this case, the FeatureAccess service layers. Thus, only users that have editing ability will have those layers show up in the web map and web app and all the remaining users get a 'view' (not editable) of the service layers.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 28 Sep 2016 16:25:07 GMT</pubDate>
      <guid>https://community.esri.com/t5/web-appbuilder-custom-widgets-questions/layer-based-authorization-in-webappbuilder-portal/m-p/778533#M2309</guid>
      <dc:creator>MichaelRobb</dc:creator>
      <dc:date>2016-09-28T16:25:07Z</dc:date>
    </item>
    <item>
      <title>Re: Layer based authorization in WebAppBuilder &amp; Portal</title>
      <link>https://community.esri.com/t5/web-appbuilder-custom-widgets-questions/layer-based-authorization-in-webappbuilder-portal/m-p/778534#M2310</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Sorry for latency,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you for your precious answers! I am going to read the articles and try them.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 05 Oct 2016 07:06:07 GMT</pubDate>
      <guid>https://community.esri.com/t5/web-appbuilder-custom-widgets-questions/layer-based-authorization-in-webappbuilder-portal/m-p/778534#M2310</guid>
      <dc:creator>BugraOtken</dc:creator>
      <dc:date>2016-10-05T07:06:07Z</dc:date>
    </item>
  </channel>
</rss>

