Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Cancel
- Home
- :
- All Communities
- :
- Products
- :
- ArcGIS Enterprise
- :
- ArcGIS Enterprise Ideas
- :
- FeatureServer level security
Options
- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Follow this Idea
- Printer Friendly Page
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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. One service, for editing, creates two endpoints: (MapServer and FeatureServer). When this service is secured, it applies the security to both the MapServer and FeatureServer. To create a public facing service, one needs to publish a second service with only the MapServer enabled. As a result, they end up with an unneeded MapServer endpoint and must maintain two separate services.
While there are times when the multiple service approach is appropriate, many times a separate service configuration for editing is unneessary.
I propose allowing security to be enabled on only the FeatureServer endpoint, removing the requirement to maintain two separate services for this workflow.
While there are times when the multiple service approach is appropriate, many times a separate service configuration for editing is unneessary.
I propose allowing security to be enabled on only the FeatureServer endpoint, removing the requirement to maintain two separate services for this workflow.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.