On Thu, Sep 22, 2016 at 4:31 PM, dimmihel <
dimitrios.michela...@improvementservice.org.uk> wrote:
> Hi again,
>
> I feel that the documentation provided in the pop-up box in the Geoserver
> GUI within /*Edit Workspace --> Services --> Workspace Specific Services*/
> needs some polishing. It is
Hi again,
I feel that the documentation provided in the pop-up box in the Geoserver
GUI within /*Edit Workspace --> Services --> Workspace Specific Services*/
needs some polishing. It is an important section for Geoserver users.
The following workflow makes a Geoserver workspace restricted to
Hi Christian Mueller-3,
Thanks for your post.
Can you elaborate on your suggestion to:
/"Put all your public WMS layers in a separate workspace and *restrict this
workspace to WMS access.*"/?
Are you talking about performing the following process?
(a) Create workspace (i.e. "public_wms")
(b)
Hi Andy
Sending username/password as URL parameters is a bad practice (think about
the browser history) and is not supported by GeoServer.
You have to do the following steps.
- add a user (optional add a user group and add the user to the group)
- add a role and and attach this role to the user
Hi Christian.
Thanks for your reply.
I wanted to use just one Workspace in order to hav one single URL to call my
services but i can live with several Worspaces.
My main issue right now is: How can i bring geoserver to ask for a password
for a specific layer (or workspace) so that i can provice
Hi Andy
I am not sure if I get my hands around your problem. My proposal would be:
Put all your public WMS layers in a separate workspace and restrict this
workspace to WMS access.
Create a workspace for protected WFS Layers and restrict access to WFS.
Now, you can add an authentication
