Security
Arbortext Publishing Engine relies on the servlet container or web application server for security. You can enhance security by placing Arbortext Publishing Engine and its servlet container or web application server on an intranet and isolating them from the internet using a firewall. Within Arbortext Publishing Engine:
• You must specify a list of Arbortext Publishing Engine application names that are allowed to be called from an HTTP request.
• You can set up a specific Windows user account under which
Arbortext PE sub-processes will run. Then you can set security permissions and restrictions on that account. For more information, refer to
Configuring a User Account.
• If you are using Tomcat, you can set up authentication for access to some of the Arbortext PE Request Manager report pages.
You must also ensure that Tomcat is configured in line with current security best practices.
• You can configure the Arbortext Publishing Engine security framework to allow or restrict requests sent to the Arbortext PE Request Manager based each request’s security classification. Security constraints are defined in the Arbortext Publishing Engine configuration file e3config.xml, working in conjunction with users and groups defined in Apache Tomcat.