idea FeatureServer level security in ArcGIS Enterprise Ideas https://community.esri.com/t5/arcgis-enterprise-ideas/featureserver-level-security/idi-p/931860 <HTML><HEAD></HEAD><BODY>Currently, if one wants to use ArcGIS Server to deploy both a secured service for editing and a public service to view the same data, they need to publish two separate services. &nbsp;One service, for editing, creates two endpoints: (MapServer and FeatureServer). &nbsp;When this service is secured, it applies the security to both the MapServer and FeatureServer. &nbsp;To create a public facing service, one needs to publish a second service with only the MapServer enabled. &nbsp;As a result, they end up with an unneeded MapServer endpoint and must maintain two separate services.<BR /><BR />While there are times when the multiple service approach is appropriate, many times a separate service configuration for editing is unneessary.<BR /><BR />I propose allowing security to be enabled on only the FeatureServer endpoint, removing the requirement to maintain two separate services for this workflow. <!-- content transformation source ID: 087E00000004JSm --> </BODY></HTML> Fri, 10 Aug 2012 14:11:40 GMT PhilHolleran 2012-08-10T14:11:40Z FeatureServer level security https://community.esri.com/t5/arcgis-enterprise-ideas/featureserver-level-security/idi-p/931860 <HTML><HEAD></HEAD><BODY>Currently, if one wants to use ArcGIS Server to deploy both a secured service for editing and a public service to view the same data, they need to publish two separate services. &nbsp;One service, for editing, creates two endpoints: (MapServer and FeatureServer). &nbsp;When this service is secured, it applies the security to both the MapServer and FeatureServer. &nbsp;To create a public facing service, one needs to publish a second service with only the MapServer enabled. &nbsp;As a result, they end up with an unneeded MapServer endpoint and must maintain two separate services.<BR /><BR />While there are times when the multiple service approach is appropriate, many times a separate service configuration for editing is unneessary.<BR /><BR />I propose allowing security to be enabled on only the FeatureServer endpoint, removing the requirement to maintain two separate services for this workflow. <!-- content transformation source ID: 087E00000004JSm --> </BODY></HTML> Fri, 10 Aug 2012 14:11:40 GMT https://community.esri.com/t5/arcgis-enterprise-ideas/featureserver-level-security/idi-p/931860 PhilHolleran 2012-08-10T14:11:40Z