-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Bad ordering of GeoFence rules #11668
Labels
Comments
12 tasks
GeoFence logs for WMS request:
|
WPS download request performs 3 calls:
|
etj
added a commit
that referenced
this issue
Nov 8, 2023
giohappy
added a commit
that referenced
this issue
Nov 9, 2023
davekennewell
pushed a commit
to Hydrata/geonode
that referenced
this issue
Nov 30, 2023
…sions (GeoNode#11669) * [Fixes GeoNode#11447] Bad role name in creating GeoFence rules * [Fixes GeoNode#11668] Bad ordering of GeoFence rules --------- Co-authored-by: Giovanni Allegri <giohappy@gmail.com> (cherry picked from commit e7b53a5)
chumano
pushed a commit
to cec-tris/geonode
that referenced
this issue
Dec 24, 2023
…sions (GeoNode#11669) (GeoNode#11677) * [Fixes GeoNode#11447] Bad role name in creating GeoFence rules * [Fixes GeoNode#11668] Bad ordering of GeoFence rules --------- Co-authored-by: Giovanni Allegri <giohappy@gmail.com> (cherry picked from commit e7b53a5) Co-authored-by: Emanuele Tajariol <etj@geo-solutions.it>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Expected Behavior
Rules applying to everyone should not have priority over specific permissions.
Actual Behavior
The download denial is applied also to registered members:
Steps to Reproduce the Problem
the Process gs:Download not allowed to operate on layer
(see comments in this issue for a full log)Specifications
The text was updated successfully, but these errors were encountered: