Bug 899368 (JBEWS-124)
| Summary: | EWS: Add sample JMX config files. | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise Web Server 1 | Reporter: | Ondřej Žižka <ozizka> | ||||||
| Component: | unspecified | Assignee: | Coty Sutherland <csutherl> | ||||||
| Status: | CLOSED EOL | QA Contact: | |||||||
| Severity: | high | Docs Contact: | |||||||
| Priority: | high | ||||||||
| Version: | EWS 1.0.2 | CC: | grocha, mjc, ozizka, pcheung | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | TBD EWS | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| URL: | http://jira.jboss.org/jira/browse/JBEWS-124 | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2017-08-04 15:06:25 UTC | Type: | Feature Request | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Attachments: |
|
||||||||
|
Description
Ondřej Žižka
2011-03-17 20:06:11 UTC
Sample files attached. Attachment: Added: jmxremote.access Attachment: Added: jmxremote.password Link: Added: This issue is related to JBPAPP-6089 Hi Ondrej, is this a docs issue? Can you please assign it accordingly? Thanks! Link: Added: This issue is related to JBPAPP-6122 Hi, not a docs issue. I'd put the sample files into the distribution archive. Mladen, any progress please? I am transfering my issues so I want to know the current status. Thx Permaine, please decide on that. If it will be part of the next release it should go into the brew Tomcat builds so this is present on all platforms. Added David from the security team on cc. David, is it ok to add these files to the EWS distribution (from a security point of view)? Permaine, I just looked at this on behalf of SRT.
The templates look good from a security perspective. However, one thing that I would like to point out is that using defaults that the user can just drop-deploy may be a security risk, as was the case for the _jmx-console_.
It might be a good idea to comment out the following lines from [^jmxremote.password] and surround them with a _WARNING_ indicating that the defaults should be changed. This would mean that at the very least the user has to un-comment the lines to get it going and hopefully reading the warning.
{noformat}
monitorRole foo
controlRole foo
{noformat}
Also note that the file permissions should be read/write for the owner only. Ideally _600_. Hope this helps.
Hi David, can you please include these files in the tomcat builds for EWS 2 (as described by Arun) when you have time? Thanks! |