I can see why this could be usefull, but I can see situations where it
would be troublesome to detect why a layer won't render.
If you haven't already done it, you can create a ticket on Trac and
request it as an enhancement.
http://trac.osgeo.org/mapguide/
Regards, Kenneth, GEOGRAF A/S
Bruno Scott skrev:
Actually when we set a no access permission on a layer definition for a given
user
and we open the map referencing this layer (using the same user ) we got
this message :
Permission denied to resource:
Library://Samples/Sheboygan/Layers/Districts.LayerDefinition
Permission denied to resource:
Library://Samples/Sheboygan/Layers/Districts.LayerDefinition Exception
occured in method MgResourceHeaderManager.CheckPermission at line 2497 in
file
c:\build_bond_area\mapguide_open_source_v1.2\build_18.1\mgdev\server\src\services\resource\ResourceHeaderManager.cpp
I know that is the intended behavior
But it would be great if the mapgudie server remove the layers with no
access on the fly.
This would gives Administrator a very high level of flexibility on
controling the security.
Just by setting security permissions on some layers or featureSource we
could control
what a specific user can see in any map
Bruno
_______________________________________________
mapguide-users mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/mapguide-users
