After some research I came to the following conclusion: MapGuide Enterprise doesn't offer you the possibility to secure WMS-layers. So normally they are accessible for everyone that knows the url http:///mapguide(X)/mapagent/mapagent.fcgi
So what I tried was to secure the WMS on the webserver level, we at the Belgian Railways are using Windows 2K3 servers with IIS. 1/ I disabled the option anonymous access 2/ I checked the option use windows authentication (so this means that the users that want to use the wms service need an account on the windows domain. 3/ When you want to use the wms as a supplementary layer in another MGE map (for example an ajax viewer or fusion viewer) you also have to provide credentials of a domain user. You have to keep in mind that in companies there's a policy that users have to reset their passwords after a month. So maybe you can ask for a domainuser for which the password doesn't expire. 4/ For external users (not part of the domain) we'll have to write a wms server as a wrapper around the MGE webservice. Users have to authenticate to access the wrapper, the MGE WMS can use the user account defined in step 3. So I hope this can be helpful for some of you experimenting with WMS Services. Kind regards, M. ----- Matthias Valcke CAD/GIS Consultant Belgian Railways (NMBS - SNCB) http://www.realdolmen.com http://n2.nabble.com/file/u288841/image001.gif -- View this message in context: http://n2.nabble.com/How-to-secure-WMS-Layers-in-MGE-tp3721492p3747487.html Sent from the MapGuide Users mailing list archive at Nabble.com.
_______________________________________________ mapguide-users mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/mapguide-users
