Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GeoServer OGC services must be under GeoNode Auth control #319

Open
gubuntu opened this issue Jan 24, 2019 · 2 comments
Open

GeoServer OGC services must be under GeoNode Auth control #319

gubuntu opened this issue Jan 24, 2019 · 2 comments
Assignees
Labels

Comments

@gubuntu
Copy link
Contributor

gubuntu commented Jan 24, 2019

Please confirm that this is the case and if not, pls organise it gets implemented

'Permission to connect to OGC service endpoints of GIS layers is assigned to groups in the GeoNode interface. Only members of groups with view access to a layer will be able to connect to that layer from an OGC client'

e.g. members of groups with view access to a layer should be able to use WMS (but not WFS or WCS)

members of groups with no access to a layer should not be able to use any OGC service.

members of groups with download access should be able to use WCS and WFS

@NyakudyaA
Copy link
Collaborator

@gubuntu This is the default behavior for Geonode. Since users have no direct access to GeoServer they access the service through a client like metasearch which will use the Geonode access token to request layers from GeoServer and give them the correct permissions.

The only major sticking point is that metasearch seems not to be working and has to be fixed

meta

@gubuntu
Copy link
Contributor Author

gubuntu commented Mar 3, 2019

@NyakudyaA please create a separate issue for Metasearch (on the QGIS repo if it is a QGIS issue) and comment on the point in the OP here.

The workflow should be for a user to see the layer view in GeoNode, look at the metadata and get the OWS url (which should be the GeoNode proxy url) from the metadata and then add the OWS service to their own GIS.

  1. The above workflow should work
  2. the correct authentication should apply as per the OP

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants