Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
This issue would only affect users that are using the Security Manager when running tomcat, and doesn't appear to affect that much. To workaround the issue users can fix the typo in the local catalina.policy; it's designated as a config file in the spec and will not be overwritten on package update.
Given the current phase of the rhel-7 lifecycle and that there hasn't been any customer interest (no attached case), I'm going to nack this. We can reassess if needed, but the workaround/fix is easy to apply locally so it shouldn't be a huge problem.
Comment 3RHEL Program Management
2020-03-31 14:03:16 UTC
Development Management has reviewed and declined this request. You may appeal this decision by using your Red Hat support channels, who will make certain the issue receives the proper prioritization with product and development management.
https://www.redhat.com/support/process/production/#howto
Description of problem: Tomcat-7.0.69-11 package contains /etc/tomcat/catalina.policy. Catalina.policy has Typo path "file:/usr/share/java/omcat-jsp-2.2-api.jar". I think /usr/share/java/tomcat-jsp-2.2-api.jar is correct. Version-Release number of selected component (if applicable): $ rpm -qa | grep tomcat tomcat-jsp-2.2-api-7.0.69-11.el7_3.noarch tomcat-el-2.2-api-7.0.69-11.el7_3.noarch tomcat-7.0.69-11.el7_3.noarch tomcat-servlet-3.0-api-7.0.69-11.el7_3.noarch tomcat-lib-7.0.69-11.el7_3.noarch How reproducible: always Steps to Reproduce: 1. $ sudo yum install tomcat 2. $ sed -n 61,63p /etc/tomcat/catalina.policy grant codeBase "file:/usr/share/java/omcat-jsp-2.2-api.jar" { permission java.security.AllPermission; }; 3. $ ls /usr/share/java/omcat-jsp-2.2-api.jar ls: cannot access /usr/share/java/omcat-jsp-2.2-api.jar: No such file or directory 4. $ ls /usr/share/java/tomcat-jsp-2.2-api.jar /usr/share/java/tomcat-jsp-2.2-api.jar Actual results: sed -n 61,63p /etc/tomcat/catalina.policy grant codeBase "file:/usr/share/java/omcat-jsp-2.2-api.jar" { permission java.security.AllPermission; }; Expected results: sed -n 61,63p /etc/tomcat/catalina.policy grant codeBase "file:/usr/share/java/tomcat-jsp-2.2-api.jar" { permission java.security.AllPermission; }; Additional info: