Select to view content in your preferred language

Feature Service shows that it is share to organization but it is shared to everyone. My data is not secure. Portal indicates that it is secure.

232
4
a week ago
DanielStark
Emerging Contributor

DanielStark_0-1746222184561.png

This shows that my feature service is shared to the organization. When examining the REST endpoint, it is shared to everybody. This is a massive security flaw.

 

DanielStark_1-1746222337526.png

 

Tags (1)
4 Replies
DavidJantz
Occasional Contributor

Unfortunately, this is working as designed. Sharing doesn't respect when the map image layer item and feature layer items are different. All "additional" functionalities inherit the permissions for the map service (map image layer). Here's a couple of posts with more details. A custom SOI (https://developers.arcgis.com/enterprise-sdk/guide/net/what-is-an-soi-net/) can provide this functionality and much more but is a bit complicated to implement.

https://community.esri.com/t5/arcgis-enterprise-ideas/allow-map-image-services-and-feature-services/...

https://community.esri.com/t5/arcgis-enterprise-ideas/ensure-security-settings-are-enforced-across-a...

 

0 Kudos
DanielStark
Emerging Contributor

Respectfully, I’m struggling to reconcile how this can be described as “working as designed” when the sharing status indicates the data is secured to the organization—when in practice, it is not.

With over 30 years of experience as an ESRI customer, I understand there may be historical context and design momentum that contributed to this situation. However, the current behavior presents a real and significant disconnect between what is shown to users and what is actually enforced. In this case, the data is not, in fact, secure—despite appearances.

RyanUthoff
MVP Regular Contributor

Perhaps "working as designed" per Esri's documentation might be a better way to put it. 

RyanUthoff_1-1746543808126.png

I'm not disagreeing with you, because it's misleading and easy to misunderstand unless you read Esri's documentation to get an understanding of how it works. I believe others have been in this situation, which is why some ArcGIS Ideas that David linked above have already been submitted for Esri to improve this. If the map image and feature layer truly are dependent on each other, then I think it would make sense for the permissions to be "linked" to each other. Meaning that if you change permissions to one, it forces you to change permissions to the other (perhaps giving you a pop-up message stating that). Otherwise, as you've encountered, it's misleading when the permissions in Portal state one thing, but in practice, are actually something else.

BillFox
MVP Frequent Contributor

workarounds for now?

  • don't make your water mains public
  • remove Query for the feature access

https://enterprise.arcgis.com/en/server/latest/publish-services/windows/editor-permissions-for-featu...

 

0 Kudos