Layer Security
@Latitude,
Currently nil security models @ layer configuration level (please correct me if i am wrong).
I was under the impression this was coming for recent release but unless I've missed it, it is still lacking. We currently are forced to duplicate sites if we have layers that we do not want ALL users to have visibility too & this solution is not ideal for many reasons.
I am hoping we get something similar to that available in ADF (ideally ability to recognized grouped layers as well). I would also expect security model to be recognized in feature services as well to control who can edit what (aka via layer visibility); would also expect workflows to honor security model as well to ensure a user can't inadvertently by-pass the security model via a workflow.
Can we have a hard & fast delivery schedule for this function as its been in the pipeline for some time now & I consider it a significant shortcoming of the current product offerings above & beyond some of the new functional enhancements we've recently seen in the product releases.
Brad
-
We have been waiting for quite awhile for this function too.
0 -
+ 1 again.......
we were told about this last December! any news we can tell our staff who are hounding us to see some important layers?
cheers
Gareth
PS. Further note: - what are LGs plans for tool based security also. ie. we don't want everyone in a site to have access to certain tools such as editing and or workflows. Avoids the need to set up multiple sites that needs replication on load balanced servers across dev/uat/prod boxes.....
0 -
Make the total +3
Sometimes separate viewers are very desirable, but other times, they are a waste. On a project I just completed, I needed 10 separate viewers. Each of the 10 was created to allow access to different feature layers and a few workflows.
It's an extreme example, but it illustrates how useful feature and tool security could be...
Dave
0
Please sign in to leave a comment.
Comments
3 comments