<html>
<head>
</head>
<body style="margin-right: 4px; font-style: normal; font-weight: normal; font-size: 12pt; margin-top: 4px; margin-left: 4px; margin-bottom: 1px; line-height: normal; font-family: Comic Sans MS; font-variant: normal">
<p style="margin-bottom: 0; margin-top: 0">
<br>
<font face="Comic Sans MS" size="3">All,</font> </p>
<br>
<p style="margin-bottom: 0; margin-top: 0">
<font face="Comic Sans MS" size="3">GeoMoose is another product to take a look at. It's possible to set up individual layers with their respective data custodial access parameters. Since all layers are abstracted to thier own MAP file, the layers themselves can be managed separately (or in groups) themselves as well. We use a folder hierarchy for this type of user access control as well as who can control publishing tasks. While GeoMoose doesn't control the access authentication directly, it's publishing storage scheme is very conducive to implementing a control structure down to the layer level, especially for roll your own authentication situations. We stuff all of our data into WebDAV for example, which has all sort of authentication methods available.</font> </p>
<br>
<p style="margin-bottom: 0; margin-top: 0">
<font face="Comic Sans MS" size="3">bobb</font> </p>
<br> <br><br>
<p style="margin-bottom: 0; margin-top: 0">
<br>
>>> Daniel Morissette <dmorissette@mapgears.com> wrote:<br> </p>
<table style="margin-right: 0; margin-left: 15px; margin-top: 0; font-size: 1em; margin-bottom: 0" bgcolor="#f3f3f3" border="0">
<tr>
<td>
<div style="padding-left: 7px; border-left: solid 1px #050505">
<p style="margin-bottom: 0; margin-top: 0">
MapServer has no built in support for securing data by users. If your<br>needs are not too complicated then it should be easy to implement<br>map-level security in your PHP and JavaScript application code. If you<br>have more advanced users/roles requirements then you may want to have a<br>look at <a href="http://geoprisma.org/">http://geoprisma.org/</a><br><br>Actually, I see that geoprisma.org seems quite slow today. You could<br>also have a look at the following demo page which also includes a short<br>intro to GeoPrisma under the [About GeoPrisma] tab:<br><a href="http://dev4g.mapgears.com/geoprisma/demo/">http://dev4g.mapgears.com/geoprisma/demo/</a><br><br>Daniel<br><br><br>On 11-03-06 06:06 AM, tigana.fluens@gmail.com wrote:<br>> What are the best practices when relating application data to MapServer<br>> data? If I have a database of users, and each user owns a specific map,<br>> what is the best way (also secure of course) of calling those maps (I'm<br>> assuming the .map files are the ones needed) that a specific user is<br>> related to? Given that:<br>><br>> - Tom has map of his real estate<br>> - Mark has map of his farm<br>> - Web app is a PHP app that uses OpenLayers as an interface to call<br>> MapServer<br>><br>> How do I manage restrictions, i.e. security?<br>> _______________________________________________<br>> mapserver-users mailing list<br>> mapserver-users@lists.osgeo.org<br>> <a href="http://lists.osgeo.org/mailman/listinfo/mapserver-users">http://lists.osgeo.org/mailman/listinfo/mapserver-users</a><br><br><br>--<br>Daniel Morissette<br><a href="http://www.mapgears.com/">http://www.mapgears.com/</a><br>Provider of Professional MapServer Support since 2000<br><br>_______________________________________________<br>mapserver-users mailing list<br>mapserver-users@lists.osgeo.org<br><a href="http://lists.osgeo.org/mailman/listinfo/mapserver-users">http://lists.osgeo.org/mailman/listinfo/mapserver-users</a><br>
</p>
</div>
</td>
</tr>
</table>
</body>
</html>