[
https://jira.jboss.org/jira/browse/JBESB-2126?page=com.atlassian.jira.plu...
]
Kevin Conner commented on JBESB-2126:
-------------------------------------
This functionality is specific to the JBoss application server so I would like to keep the
implementation out of the pipeline. The interface you are suggesting look fine from what
I can see, if you feel this is appropriate then go with it.
By wrapping I meant to enclose the execution of the pipeline in a try/finally such as
pushCredentials
try
{
...
}
finally
{
popCredentials
}
I wasn't meaning anything more complicated.
JBoss security credentials not always initialised
-------------------------------------------------
Key: JBESB-2126
URL:
https://jira.jboss.org/jira/browse/JBESB-2126
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Security
Affects Versions: 4.4 CP1
Reporter: Kevin Conner
Assignee: Daniel Bevenius
Fix For: 4.4 CP1
The JBoss security credentials are not always propagated.
The current code is pushing the context within the authentication but there are a couple
of issues with this.
- authentication is not always performed (if a security context exists)
- there is not attempt to 'pop' these credentials when finished.
This functionality should be pushed into the pipeline, through an implementation(s)
configured from jbossesb-properties.xml, and wrap the execution.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira