Bug 1485308
| Summary: | [regression] tomcat fails to start via tomcat-jsvc service startup due to selinux denials [rhel-7.4.z] | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Oneata Mircea Teodor <toneata> |
| Component: | selinux-policy | Assignee: | Lukas Vrabec <lvrabec> |
| Status: | CLOSED ERRATA | QA Contact: | Milos Malik <mmalik> |
| Severity: | high | Docs Contact: | Ioanna Gkioka <igkioka> |
| Priority: | high | ||
| Version: | 7.4 | CC: | csutherl, dmoppert, igkioka, jonderka, lvrabec, mbabacek, mgrepl, mjahoda, mmalik, mthacker, plautrba, pvrabec, ssekidde, toneata, troels, twalsh |
| Target Milestone: | rc | Keywords: | ZStream |
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | selinux-policy-3.13.1-166.el7_4.4 | Doc Type: | Bug Fix |
| Doc Text: |
In Red Hat Enterprise Linux 7.4, the Tomcat server was not running unconfined, and SELinux security policy was enforced by SELinux. As a consequence, Tomcat failed to start through the tomcat-jsvc service due to SELinux. This update allows the tomcat_t SELinux domain to use the dac_override, setuid, kill capability rules. As a result, Tomcat starts correctly through tomcat-jsvc with SELinux in enforcing mode.
|
Story Points: | --- |
| Clone Of: | 1470735 | Environment: | |
| Last Closed: | 2017-09-05 11:26:11 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 1470735 | ||
| Bug Blocks: | |||
|
Description
Oneata Mircea Teodor
2017-08-25 11:05:30 UTC
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2017:2579 |