[esb-issues] [JBoss JIRA] Commented: (JBESB-2126) JBoss security credentials not always initialised
[
https://jira.jboss.org/jira/browse/JBESB-2126?page=com.atlassian.jira.plu...
]
Daniel Bevenius commented on JBESB-2126:
----------------------------------------
This functionality should be pushed into the pipeline, through an
implementation(s) configured from jbossesb-properties.xml, and wrap the execution.
Hey Kev, can you expand on what you had in mind here?
Do you mean that we create an interface, something like:
/**
* A SecurityContextPropagator can push/propagate and pop/remove security context
* information to a specified targets security subsytem.
* </p>
* For example, a SecurityContextPropagator for JBossAS would propagate a security
* context so that it is made available to JBossAS Security subsystem.
*
* @author <a href="mailto:dbevenius@jboss.com">Daniel Bevenius</a>
*/
public interface SecurityContextPropagator
{
/**
* Push/Propagate the Security context information to the destined system.
*
* @param context The security context to be pushed(propagated)
*/
void pushSecurityContext(final SecurityContext context, final SecurityConfig config);
/**
* Pop/Remove the Security context information to the destined system.
*
* @param context The security context to be pushed(propagated)
*/
void popSecurityContext(final SecurityContext context, final SecurityConfig config);
}
A concrete impl can be specified in jbossesb-properties.xml.
We then push the security context whenever a valid SecurityContext exists and not only
upon authentication as it is at the moment.
And we also make sure that we pop the context after the action pipeline completes. Is that
what you meant with "wrap" of was there something more to it than that.
Thanks
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