SuperContainer Server on mixed internal external Network

[cat traveller]

Hello everyone,

I am stuck in trying to make the following possible:

Currently, we have a corporate database on a filemaker server 11 (not advanced) that uses SupercontainerServer that is used by our team. They access the database

from the internal IP, lets say 192.168... supercontainer on SCSetBaseUrl is set in the startup script with 192.168... as well (internal network).

Now, we are making this database available on the internet in order for our second office (our kitchen) to use it as well.

Hence, the db is available via, say 178 (external ip) from port 5003 (there is a port forwarding rule to the 192 ip).

Since fmServer is set to SSL encrypt traffic and we are using strong passwords, I think we are ok.

How can I make SupercontainerServer work without making port 80 open for everyone to see on the internet (that would be a security issue, right?).

I am looking for a very secure option, since this is corporate data afterall. Is this possible at all?

Thanks

ole

[Smef]

The easiest thing to do would be to set a username and password on your SuperContainer server. This would still open port 80 in your firewall, but would protect your documents. Your only other option would be to set up a VPN if you don't want to make it available to the internet.