Layer-level permissions?
Hi,
We have a need for listing layers in the map based on role. We plan to have a few roles (Geocortex role provider, but might change if need be) that would correspond to what layers the user is allowed to view (ie Utility authenticated users can see utility layers). (This also will extend to reports in the Silverlight viewer as well where only certain people can run parcel reports and such). Can someone confirm this functionality is not out-of-the-box? Would there be a recommended way to handle this?
Like, is there a way to trap some layers loading event and cancel or remove specific ones based on some criteria? Or is is configurable somehow? Right now I'm just looking for ideas that have worked for people.
Thanks a lot
-
i'll answer my own question...haven't totally figured it out, but at least i know i can hook into the AuthenticationSucceededEvent event and SiteInitializedEvent and between the two with the addition of layer properties possibly, I can add/remove layers/tools at will.
0 -
Hi Irene,
Out of the box layer level authorization is currently under development. This should be available early in 2013.
If you need something immediately and are up for a bit of coding you can subscribe to the SiteInitializedEvent and remove layers from the application. Or you can use a startup workflow and the GetCurrentUser activity followed by a custom activity to do the same. With these approaches you will just be hiding the layers so they don't appear for the user. The ArcGIS Server endpoints will remain unsecured.
--Ryan
0 -
Thanks,
Yeah, that's just what I've done...created a workflow to retrieve the user and roles, then (in the silverlight api) upon site initialization, run the workflow then decide what to do with the layers (not finalized yet, but probably assign a csv list of roles via property to each special layer or something). I have my map services secured through ArcGIS tokens, so technically I guess an authenticated GE user has an ArcGIS token that it is possible to see data that they are not authorized for. If there is a better solution, please let me know. I think in our scenario for now, that is fine.
Thanks again
0
Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.
Kommentare
3 Kommentare