Bug 997009
Summary: | requiredSecret attribute on the AJP connector | |||
---|---|---|---|---|
Product: | [JBoss] JBoss Enterprise Application Platform 6 | Reporter: | Tom Fonteyne <tfonteyn> | |
Component: | Web | Assignee: | Tom Fonteyne <tfonteyn> | |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Radim Hatlapatka <rhatlapa> | |
Severity: | medium | Docs Contact: | ||
Priority: | unspecified | |||
Version: | 6.1.0 | CC: | myarboro | |
Target Milestone: | ER1 | |||
Target Release: | EAP 6.2.0 | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | Doc Type: | Bug Fix | ||
Doc Text: |
When using a load balancing Apache server in front of JBoss EAP 5.x, you can set the "requiredSecret" attribute of the AJP connector. This is used to only allow requests from load-balancer workers with the same secret keyword, to be accepted.
In JBoss EAP 6.0.x and 6.1.x it was not possible to configure this value. This issue has now resolved and you can now set a system property to your required value for the "requiredSecret" attribute:
----
org.apache.coyote.ajp.DEFAULT_REQUIRED_SECRET=yoursecretvalue
----
|
Story Points: | --- | |
Clone Of: | ||||
: | 1005130 (view as bug list) | Environment: | ||
Last Closed: | 2013-12-15 16:19:58 UTC | Type: | Bug | |
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: | ||||
Bug Blocks: | 1005130 |
Description
Tom Fonteyne
2013-08-14 13:23:19 UTC
$ svn ci -m "[bz-997009] allow configuration of requiredSecret attribute on the AJP connector with a system property" Sending src/main/java/org/apache/coyote/ajp/AjpAprProtocol.java Sending src/main/java/org/apache/coyote/ajp/AjpProtocol.java Sending src/main/java/org/apache/coyote/ajp/Constants.java Transmitting file data ... Committed revision 2246. Verified with EAP 6.2.0.ER1 *** Bug 997007 has been marked as a duplicate of this bug. *** |