Graham Humphries created an issue |
Issue Type: |
Bug |
---|---|
Affects Versions: |
2.19-RC, 2.19.0, 2.19.1 |
Assignee: |
Unassigned |
Components: |
Configuration |
Created: |
10/Jun/21 2:20 AM |
Environment: |
Oracle Solaris 5.11 sparcv9, Tomcat 8.5.60, AdoptOpenJDK 1.8.0_275-b01 |
Priority: |
Medium |
Reporter: |
I have set the Proxy Base URL in the Geoserver Global Settings to and the Edit Workspace page to my external URL like https://<myorg>.tas.gov.au/geoserver. This is to allow the differentiation of internal and external users and apply the correct authorisation without requiring users to create a login profile. This configuration has been working since Geoserver 2.11 Since the release of Geoserver 2.19.nn the UI behaviour has changed. If I log in using my internal URL eg http://<server name>:8080/geoserver geoserver redirects to my external URL above. This causes a problem because any Geoserver request that is reverse proxied also has a user authorisation added to the request header. This user obviously does not have an admin role, so I can’t make changes to Geoserver. I have tested Geoserver versions 2.18.1, 2.18.2, 2.18.3 2.19.RC, 2.19.0 & 2.19.1. It is only the Geoserver versions 2.19.nn that do this. Can the previous behaviour be restored? |
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#100166-sha1:b9531e5) |