Hi Ovia
This is not possible with GeoServer 2.2.x series, try the 2.3-beta1 or a nightly build.
Starting with 2.3, you can add and rearrange filter chains. There are 2 possibilities to access a workspace
1) http://…/geoserver/wfs?request=getcapabilities&workspace=<myWorkspace>
or
2) http://…/geoserver/<myWorkspace>/wfs?request=getcapabilities
Version 2) is covered by filter chain mapping. You have to add a chain with a list of Ant patterns covering your public chains. (/myworkspace/wfs/**,....).
Put the anonymous filter on this chain.
On the default chain (/**) you have to put a real authentication filter (basic,digest,...). The default chain has to be the last in the list.
Hope that helps
PS: There is no documentation at this point in time.
Christian
Zitat von "Hakala Oiva (MTT)" <oiva.hakala@anonymised.com>:
Hi everyone
I have tried and tried this: to put maps belonging to a certain workspace behind a password, but so far without any success.
The idea is that most of the maps are usable WITHOUT any password, but only maps belonging to one workspace need username and password. I have read all the documents.
If I create a user with ROLE_GROUP_ADMIN role, and use data security rule <workspace>.*.r=ROLE_GROUP_ADMIN, all the workspaces are behind a password despite of the other rules in Data Security.
In Authentication Filter Chains (Request Chain) menu "default" is selected and in selected box on the right "basic" is selected.
With these settings all workspaces are behind a username and password, which is not wanted.
So, could anyone help me with this mess? I am an advanced IT person, but I cannot solve this problem, although I have read all the documents. I have not found a single working example on the net.
Oiva
----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.