|
|
Nuno Oliveira created an issue |
|
Security data read rules may wrongly hide virtual services configuration |
|
Issue Type: |
|
|---|---|
|
Assignee: |
Unassigned |
|
Attachments: |
image-2018-01-17-11-04-30-226.png, image-2018-01-17-11-07-24-035.png, image-2018-01-17-11-20-12-609.png |
|
Components: |
Security |
|
Created: |
17/Jan/18 12:22 PM |
|
Priority: |
|
|
Reporter: |
|
This one is a bit weird. First of all, by virtual services configuration I mean the configuration that can be applied to a certain service (WMS, WFS,etc …) virtual endpoint corresponding to a certain workspace: With the default GeoServer security data rules everything works has expected: This rules basically say that everyone has the right to read everything but only administrators can write. But if I define this rules: This rules have exactly the same meaning of the default ones, we are just explicitly selecting all the concerned roles. In this case it will not be possible to view virtual services specific configuration, but it wil be possible to override the existing one. Another strange thing, is that changing security data rules requires a GeoServer for those rules to affect GeoServer virtual services configuration access. |
|
|
|
Get Jira notifications on your phone! Download the Jira Cloud app for Android or iOS |
|
|
This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100076-sha1:50f5bce) |
|
|
|