• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Tomcat Security

J

JosephB

Guest
I see that the Tomcat service is running as the system administrator, which grants the Tomcat service root access. While testing Tomcat I also found that through your applications you can actually write to any folder on the drive. Is this not a major security risk? What steps must I take to secure Tomcat and possibly set the service to use a restricted user account?
 
I am quite surprised and disappointed by the poor design of the Tomcat integration, although I am still optimistic towards setting-up up a secure and reliable Tomcat environment. For now I modified the Tomcat service to run as a separate user account to deny it access to system files.

If anyone has any comments regarding securing or setting up Tomcat on Plesk for Windows then please let me know.
 
Back
Top