Skip to end of banner
Go to start of banner

How do I expose Web UI's of netFIELD App containers in a secure way when running on hosts that are not supporting netFIELD OS (e.g.using nginx)?

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Current »

Q

How do I expose Web UI's of netFIELD App containers in a secure way when running on hosts that are not supporting netFIELD OS (e.g.using nginx)?

A

When using netFIELD Apps on hosts that are not supporting Hilscher's "netFIELD OS" operating system it is up to the end-user to implement an appropriate mechanism to expose the apps' Web UI ports (usually coming without https:// support) in a secure way.

The most effective and easy solution is to use an nginx reverse proxy (installable also as a container) as the secure bridge between the inner container "bridged" network and the host's network available from outside.

Nginx is able to offer a broad range of security controls that most likely match nearly all end-user needs: https://docs.nginx.com/nginx/admin-guide/security-controls/

The overall setup then may look like the following illustration shows: only a single nginx port needs to be exposed TLS secured as https:// and routes accesses to subordinate application containers

  • No labels