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 - adding fqdn to the geoserver's CSRF whitelist #60

Merged
merged 1 commit into from
Nov 2, 2023

Conversation

pmauduit
Copy link
Member

See https://docs.geoserver.org/main/en/user/security/webadmin/csrf.html for the motivation.

Also please note that in case of using the geOrchestra gateway, the default http header for the referrer-policy will be "no-referrer", which prevents wicket to determine if the request is legit or not (the check is based on the referer or origin http headers). so to make sure the referer header is provided, this requires the following configuration property to be set on the gateway as well:

spring.cloud.gateway.filter.secure-headers=strict-origin (or something
  laxer than no-referrer, see mdn doc for possible values)

Note: I wonder if one needs to customize the value, maybe we need another value in the values.yaml ?

See https://docs.geoserver.org/main/en/user/security/webadmin/csrf.html
for the motivation.

Also please note that in case of using the geOrchestra gateway, the
default http header for the referrer-policy will be "no-referrer", which
prevents wicket to determine if the request is legit or not (the check
is based on the referer or origin http headers). so to make sure the
referer header is provided, this requires the following configuration
property to be set on the gateway as well:

```
spring.cloud.gateway.filter.secure-headers=strict-origin (or something
  laxer than no-referrer, see mdn doc for possible values)
```
@edevosc2c
Copy link
Member

Can't this be configured inside the datadir?

@pmauduit
Copy link
Member Author

Can't this be configured inside the datadir?

If you open the geoserver documentation pointed above, no. Only 3 methods are available, and the env variable is the most convenient IMHO (first one requires to hack the web.xml, second one is using a java property, which can also be done though but does not provide any added value compared to using an env variable).

@edevosc2c edevosc2c merged commit e1fe62a into main Nov 2, 2023
1 check passed
@edevosc2c edevosc2c deleted the gs_add_csrf_whitelist_fqdn branch November 2, 2023 14:29
f-necas added a commit to georchestra/datadir that referenced this pull request Apr 9, 2024
f-necas added a commit to georchestra/datadir that referenced this pull request Apr 11, 2024
@edevosc2c edevosc2c added the enhancement New feature or request label Jul 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants