OneGate is run by the http server on your system. It also uses directories and files for various functions. Thus, the directories and files should be accessible to the User ID that httpd runs as, as well as the applications that it calls. Both OneGate and the applications it calls must be able to read and write to these locations.

Many times, this can be achieved by simply making the files and directories owned by the httpd-running user. However, there are circumstances in which you might be calling a program that needs to run SUID as another user.

In cases like this, you have several options:

• If you use Apache, you could use something like the suEXEC facilities.
• You can use an application like CGIWrap. I use this option myself, and have had no difficulties with it, even under unusual configuration requirements.
• If you administer the system and you are implementing a web server dedicated to one particular task, you can make httpd run as the required user that matches what your application requires.

If you have concerns regarding this issue, you can contact us at onegate@fairlite.com and we will assist you in finding the solution that's best for your situation.