If you wish to provide more robust security for reports generated by Project Reporter, you should configure it to work with one of the supported third-party web servers, which have more advanced support for user authentication and request filtering. You can also make use of supplementary security tools such as network firewalls and directory permissions.
Here are some examples of how you might configure Project Reporter for different user environments:
||No special configuration required use a stand-alone web server such as Apache Tomcat, and let all users enter as Guest (each user still requires a separate client license)|
||Use the stand-alone web server, but disable the Guest account and create separate report views with and without cost information included. Create separate individual or shared user accounts for users who should or should not have access to cost information, and assign the views appropriately to these accounts. Optionally, set operating-system permissions on directories used as data sources by Project Reporter, to prevent unauthorized direct access to project files via a shared file system.|
||Use the stand-alone web server if you have a closed extranet, or configure a server such as Apache Tomcat with a third-party web server or SSL to restrict outside access to certain domains or users.|
||Use the stand-alone web server and/or a third-party web server or SSL, and create a link from your home page which logs all users in as Guest (requires unlimited-client license).|
Administering Project Reporter