Is there any way to configure SuperContainer to work with mod_access so that allow and deny directives can be used? I tried setting up a Directory section in my apache config with order, deny, and allow directives directly to my supercontainer data directory (/Volumes/Data/SuperContainer), but I didn't have any luck.

Thanks,

Jeremy

I don't think you will be able to use mod_access, b/c it's Tomcat that executes the SuperContainer web application which then accesses the files on disk.

What are you trying to achieve?

The idea is to protect the documents so that they are only accessible via internal access. We host multiple sites on the server and the other sites all need to be available via external access. Mod_access would enable this to work, but I couldn't figure out a way to implement due to the fact that the SuperContainer stuff isn't setup as an actual site in Apache.

SuperContainer does not need to run on the same machine as your filemaker server, so a separate, stand-alone SuperContainer deployment might work for you, or a Tomcat deployment that is not accessible from ourside of your network. This way you can control access to SuperContainer simply by not allowing the ports it is working on to be accessed from outside your network. You could set up SC on a machine which only is accessible internally, or is using an internal IP address.

SuperContainer running in stand alone mode runs on port 8020 by default. Instructions for deploying SuperContainer with Tomcat can be found as deployment option 3 in the SuperContainer documentation.

Edited June 25, 201015 yr by Guest