With an external domain, the geoserver oauth is not working correctly: an error message complains about the redirect_uri which does not match what is registered in geonode, because of an additional /.
Reproduction Steps
best to provide your values.yaml, a brief description of your cluster and version of geonode-k8s here.
Behavior
After login with oauth in GeoServer, we should be redirected to the GeoServer home page.
Additional Information
The problem is related to the init scripts of GeoServer which configures the OAuth2 GeoNode filter. The scripts use the variable NGINX_BASE_URL to define the GEOSERVER_URL and add a ending slash to the value provided by NGINX_BASE_URL. As a consequence the configuration points for the filtre contain two slashes, which differs from the configuration defined on the GeoNode side.
Bug Description
With an external domain, the geoserver oauth is not working correctly: an error message complains about the redirect_uri which does not match what is registered in geonode, because of an additional /.
Reproduction Steps
best to provide your values.yaml, a brief description of your cluster and version of geonode-k8s here.
Behavior
After login with oauth in GeoServer, we should be redirected to the GeoServer home page.
Additional Information
The problem is related to the init scripts of GeoServer which configures the OAuth2 GeoNode filter. The scripts use the variable NGINX_BASE_URL to define the GEOSERVER_URL and add a ending slash to the value provided by NGINX_BASE_URL. As a consequence the configuration points for the filtre contain two slashes, which differs from the configuration defined on the GeoNode side.