Bug 778390 (SOA-873) - SOA-P platform bug for: http://jira.jboss.com/jira/browse/JBPAPP-544
Summary: SOA-P platform bug for: http://jira.jboss.com/jira/browse/JBPAPP-544
Keywords:
Status: CLOSED NEXTRELEASE
Alias: SOA-873
Product: JBoss Enterprise SOA Platform 4
Classification: JBoss
Component: Security
Version: 4.2 Beta 1
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.2 CP03
Assignee: Jim Ma
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-09-26 06:29 UTC by nwallace
Modified: 2014-05-27 01:27 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-12-11 16:09:05 UTC
Type: Bug

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 777803 0 high CLOSED SOA-P platform bug for: http://jira.jboss.com/jira/browse/JBPAPP-544 2021-02-22 00:41:40 UTC
Red Hat Issue Tracker SOA-873 0 None None None Never

Internal Links: 777803

Description nwallace 2008-09-26 06:29:54 UTC 
Date of First Response: 2008-11-05 22:17:28
project_key: SOA

http://jira.jboss.com/jira/browse/JBPAPP-544 describes a problem in the EAP release - unprotected servlets. The SOA-P release will share the same problem.
Comment 1 nwallace 2008-09-26 06:29:54 UTC 
Link: Added: This issue depends JBPAPP-544
Comment 2 nwallace 2008-09-26 06:30:25 UTC 
Link: Added: This issue is related to SOA-329
Comment 3 nwallace 2008-09-26 06:30:56 UTC 
Can we have confirmation that fixes are in place for 4.2CP03.
Comment 5 Dana Mison 2008-11-25 06:25:34 UTC 
Release Note: The Status Servlet for the embedded Tomcat server now requires authentication.
Comment 6 Len DiMaggio 2008-12-11 16:09:05 UTC 
Verified fixed in 4.2 CP03 CR5

http://host:8080/status?full=true   

returns a 404 error

The user must use 

http://host:8080/web-console/status?full=true 

which does require authentication
Note You need to log in before you can comment on or make changes to this bug.