-
Notifications
You must be signed in to change notification settings - Fork 39
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
Demo to set SSL properly in NGINX #105
Comments
@davebulaval sorry for the ignorance, this means that is not possible to have GN deployed with docker to run over httpS? |
@davebulaval also what the above means? Is there any doc that states clearly that the docker version can't do httpS? |
Right now, it seems like the Jetty server around the Docker image of GeoNetwork does not support natively HTTPS requests. The container always redirects HTTP request even if my NGINX handle HTTPS properly. Thus, if one wants to use OAUTH, the redirect link is HTTP thus, it fails. Our next step was to try to inject config in the Jetty server but we have never used Jetty or TomCat. |
Been a couple of days since I wrote this. My guess is that in some issue/discussion, you (or someone in the organization) explained this. I'll try to find it again. EDIT*: I think it is this thread geonetwork/core-geonetwork#6947. |
@davebulaval thanks! |
Can any GN developer comment on this? |
Hello, any update about the issue related to the redirect_uri under http instead of https? |
I've been trying to deploy a GeoNetwork (GN) using the docker-compose on an Azure VM with OAuth authentification, and I have difficulty with the redirect URL.
My current hypothesis is that since we use the default GN image container, it comes in a Jetty image that does not support the HTTPS request nor properly handle the HTTP into HTTPS redirect (as you explained); thus, URLs are not correctly handled.
Is there a way to inject configuration to Jetty in the docker image?
If I want to package my own GN image in a Dockerfile, what do I need?
Is there a way to have an image with an HTTPS Jetty directly from this image repository (in the future) for easier production use?
The text was updated successfully, but these errors were encountered: