How to configure HTTPS and add CA issued SSL certificate to docker containers of FME Server 2018?
Is there a better option than configuring manually and adding persistent volumes for changed folders?
Solved
Add HTTPS to FME Server docker
Best answer by gerhardatsafe
Hi @andrey,
with the currently available containers, tomcat configuration files would need to be changed and persisted, which is a challenge if you already noticed.
I talked to the developers and we expect to release new FME Server for Docker containers shortly after the official 2018.1 release which will come with HTTPS configuration by default. So I would recommend waiting for these new containers as it will not only be way easier to implement but you will also have a deployment configured for SSL that has been thoroughly tested by us.
We will post an update here once they are available.
UPDATE:
A Docker Compose deployment using our new containers for 2018.1 including a NGINX container as reverse proxy with default SSL configuration is now available:
Here is also some public documentation regarding the new deployment options.
Please let us know if you have any comments or questions!
Hi @andrey,
with the currently available containers, tomcat configuration files would need to be changed and persisted, which is a challenge if you already noticed.
I talked to the developers and we expect to release new FME Server for Docker containers shortly after the official 2018.1 release which will come with HTTPS configuration by default. So I would recommend waiting for these new containers as it will not only be way easier to implement but you will also have a deployment configured for SSL that has been thoroughly tested by us.
We will post an update here once they are available.
UPDATE:
A Docker Compose deployment using our new containers for 2018.1 including a NGINX container as reverse proxy with default SSL configuration is now available:
Here is also some public documentation regarding the new deployment options.
Please let us know if you have any comments or questions!
gerhardatsafe wrote:
Hi @andrey,
with the currently available containers, tomcat configuration files would need to be changed and persisted, which is a challenge if you already noticed.
I talked to the developers and we expect to release new FME Server for Docker containers shortly after the official 2018.1 release which will come with HTTPS configuration by default. So I would recommend waiting for these new containers as it will not only be way easier to implement but you will also have a deployment configured for SSL that has been thoroughly tested by us.
We will post an update here once they are available.
UPDATE:
A Docker Compose deployment using our new containers for 2018.1 including a NGINX container as reverse proxy with default SSL configuration is now available:
Here is also some public documentation regarding the new deployment options.
Please let us know if you have any comments or questions!
andrey wrote:
Thanks @GerhardAtSafe! When the new release is expected?
gerhardatsafe wrote:
The new containers with 2018.1 should be available within 4 - 6 weeks.
gerhardatsafe wrote:
The new containers with 2018.1 should be available within 4 - 6 weeks.
tburke_gcpud wrote:
Looks like 2018.1 bits are out, is there any documentation on how to configure this?
Reply
Rich Text Editor, editor1
Editor toolbars
Press ALT 0 for help
Helpful Members This Week
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.