Hi,
Is it possible to configure layers so that they are only served through
specified services? I could imagine situations when it is OK the show a map
through WMS but the original data should not be downloadable through WFS. Or the
main purpose is to deliver vector data and showing that via WMS is useless. I
cannot see any this kind of selections in server administration tool. Is it
something that should go through user rights management system?
-Jukka Rahkonen-
Hello,
For me, it seems you can only prevent user from accessing the WMS service or the WFS service but you can not choose this for each layer.
I think that a solution to handle this is to have two geoserver instances, one providing the WMS service and one other providing the WFS service and you register the appropriate layers in the service you want.
Alexandre
On Fri, Apr 4, 2008 at 10:29 AM, Jukka Rahkonen <jukka.rahkonen@anonymised.com> wrote:
Hi,
Is it possible to configure layers so that they are only served through
specified services? I could imagine situations when it is OK the show a map
through WMS but the original data should not be downloadable through WFS. Or the
main purpose is to deliver vector data and showing that via WMS is useless. I
cannot see any this kind of selections in server administration tool. Is it
something that should go through user rights management system?-Jukka Rahkonen-
Check out the new SourceForge.net Marketplace.
It’s the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
Is it possible to configure layers so that they are only served through
specified services?
Try to configure the server to activate only the service you need,
i.e. only WMS and not WFS.
I suppose that this works, although for my little tests WMS is always enabled.
Try to configure the server to activate only the service you need,
i.e. only WMS and not WFS.
I suppose that this works, although for my little tests WMS is always enabled.
Sorry I've read the mail better, and for each layer my trick don't works
Hello,
The activation/desactivation of the services works fine. You can also let the two services available and secure them with a password.
Alexandre
On Fri, Apr 4, 2008 at 10:44 AM, Diego Guidi <diegoguidi@anonymised.com> wrote:
Is it possible to configure layers so that they are only served through
specified services?Try to configure the server to activate only the service you need,
i.e. only WMS and not WFS.
I suppose that this works, although for my little tests WMS is always enabled.
Check out the new SourceForge.net Marketplace.
It’s the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
Alexandre Gacon <alexandre.gacon <at> gmail.com> writes:
Hello,For me, it seems you can only prevent user from accessing the WMS
service or the WFS service but you can not choose this for each layer.I think
that a solution to handle this is to have two geoserver instances, one providing
the WMS service and one other providing the WFS service and you register the
appropriate layers in the service you want.Alexandre
OK, so it is all or nothing. I suppose that having two instances is not too
difficult for users. Usually they need to write connection URLs for WMS and WFS
services to different dialogs anyway.
-Jukka Rahkonen-
Yep,
you're probably right. There's no data level security system in Geoserver, which the layer level security would be, right?
But there should be. Like combined service/data level security module so that you could define starting from layer level its service level security. It would be useful, I believe.
Day-dreaming again..?
reg.
mika
Jukka Rahkonen kirjoitti:
Alexandre Gacon <alexandre.gacon <at> gmail.com> writes:
Hello,For me, it seems you can only prevent user from accessing the WMS
service or the WFS service but you can not choose this for each layer.I think
that a solution to handle this is to have two geoserver instances, one providing
the WMS service and one other providing the WFS service and you register the
appropriate layers in the service you want.AlexandreOK, so it is all or nothing. I suppose that having two instances is not too
difficult for users. Usually they need to write connection URLs for WMS and WFS
services to different dialogs anyway.-Jukka Rahkonen-
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
Lehtonen, Mika ha scritto:
Yep,
you're probably right. There's no data level security system in Geoserver, which the layer level security would be, right?
But there should be. Like combined service/data level security module so that you could define starting from layer level its service level security. It would be useful, I believe.
Day-dreaming again..?
Having a per feature type security configuration is something that's
obviosly beneficial to a large set of use cases.
The main issue here is that none of the organisations sponsoring
GeoServer development is in need of such a functionality right now,
and all developers are busy following other priorities at the moment.
So yes, I'm all for having that kind of functionality, the problem
is finding someone to either code or sponsor it.
Cheers
Andrea
MassGIS is also interested in limiting WFS (for example, for certain layers
to 1 or some number of features per request). My great hope is for our
organization to be able to help sponsor bug fixes and enhancements in the
future.
--
View this message in context: http://www.nabble.com/How-to-serve-layers-only-through-WMS-of-WFS--tp16491856p16537527.html
Sent from the GeoServer - User mailing list archive at Nabble.com.
aleda_freeman ha scritto:
MassGIS is also interested in limiting WFS (for example, for certain layers
to 1 or some number of features per request).
This you can already do since GeoServer 1.6.1. You have a global maxFeature limit, and a per feature type one as well.
So if you want people to be able and download just one feature, you can
already.
My great hope is for our
organization to be able to help sponsor bug fixes and enhancements in the
future.
Sponsoring is always welcomed 
Cheers
Andrea
Andrea Aime wrote:
This you can already do since GeoServer 1.6.1. You have a global maxFeature
limit,
and a per feature type one as well. So if you want people to be able and
download
just one feature, you can already.
I downloaded 1.6.2, and tried it with a shapefile and it worked beautifully.
There's a max
features box on the web interface form for the featureType, I specified 4
and
<maxFeatures>4</maxFeatures> is written into the info.xml. Afterwards,
GetFeature
with either shapefile output or using CQL in the URL or XML WFS query all
were limited to
4 features. No max feature information is put into the GetCapabilities
document, but that's
OK with me. It should be obvious to the user that they're not getting
everything.
--
View this message in context: http://www.nabble.com/How-to-serve-layers-only-through-WMS-of-WFS--tp16491856p16570576.html
Sent from the GeoServer - User mailing list archive at Nabble.com.