[JBoss JIRA] Created: (SECURITY-573) Improve handling of IOException thrown from NegotiationAuthenticator
by Marek Posolda (JIRA)
Improve handling of IOException thrown from NegotiationAuthenticator
--------------------------------------------------------------------
Key: SECURITY-573
URL: https://issues.jboss.org/browse/SECURITY-573
Project: PicketBox (JBoss Security and Identity Management)
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Negotiation
Affects Versions: Negotiation_2.0.3.GA
Environment: JBoss EPP 5.1.GA with SPNEGO support, JBoss Negotiation 2.0.3, commons-http-client 3.1 used as HTTP client
Reporter: Marek Posolda
Assignee: Darran Lofthouse
Fix For: Negotiation_2.0.4
Currently if IOException is thrown from NegotiationAuthenticator (For example from line 123 from statement: NegotiationMessage requestMessage = mf.createMessage(authTokenIS); )
then this exception is never logged but it's catched and ignored in CoyoteAdapter.service. Result is that client receives response code 200 OK and emtpy HTTP response. And there is nothing in server log, which can be used to recognize error. So I need to debug if I want to find the real cause of IO issue.
Example for simulating of this issue can be using of Kerberos OID instead of SPNEGO OID as described in Jira SECURITY-572
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 6 months
[JBoss JIRA] (AS7-2506) Domain Model Visulaization
by Pat McDonough (Created) (JIRA)
Domain Model Visulaization
--------------------------
Key: AS7-2506
URL: https://issues.jboss.org/browse/AS7-2506
Project: Application Server 7
Issue Type: Feature Request
Components: Console
Reporter: Pat McDonough
Assignee: Heiko Braun
Provide a visual/graphic model of the current domain model.
The model would visually indicate things such as:
* Hosts
* App Servers
* JVM processes and parameters
* Highlight the domain controller
* Display host controller info
* Active Profiles
* Network interfaces
* ?Clusters?
Each of the components could provide additional contextual info and hyperlinked
If done well, this would serve as a great landing page for console.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 7 months
[JBoss JIRA] Created: (JBRULES-3083) DecisionTable incorrectly parsed with 5.2.0.CR1
by Kara Melba (JIRA)
DecisionTable incorrectly parsed with 5.2.0.CR1
-----------------------------------------------
Key: JBRULES-3083
URL: https://issues.jboss.org/browse/JBRULES-3083
Project: Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 5.2.0.CR1
Reporter: Kara Melba
Assignee: Mark Proctor
5.2.0.CR1 creates incorrect drl from decition table. With 5.1.0.M1 the drl for the same decision tables is correct.
Wrong DRL from 5.2.0.CR1:
rule "ProcessState"
salience 65522
ruleflow-group "CompleteSubOrder"
activation-group "ProcessState"
when
$m:ModifiedMarker(processState==null, state ==null)
$s:SubOrder
then
$m.setIsModified(true);
$s.setProcessState(ProcessState.CREATED);
end
Correct DRL with 5.1.0.M1:
rule "ProcessState"
salience 65522
ruleflow-group "CompleteSubOrder"
activation-group "ProcessState"
when
$m:ModifiedMarker()
$s:SubOrder(processState==null, state ==null)
then
$m.setIsModified(true);
$s.setProcessState(ProcessState.CREATED);
end
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 7 months