[
https://jira.jboss.org/jira/browse/JBESB-1992?page=com.atlassian.jira.plu...
]
Kevin Conner commented on JBESB-1992:
-------------------------------------
The security should already be unified as that was always the intent.
The 'bug' is that we have gone down two differing paths in implementing this and
it should not have happened.
EBWS Security needs rework and unification
------------------------------------------
Key: JBESB-1992
URL:
https://jira.jboss.org/jira/browse/JBESB-1992
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Rosetta, Security, Web Services
Affects Versions: 4.4
Reporter: Jiri Pechanec
Priority: Critical
There is now security implementation at two levels
- specifying webservice="security" attribute enables JBossWS security
handler
- specifying security elemnt enables WSSecuritySoapExtractor
The WSSecuritySoapExtractor operates at XML/DOM level which means that is completely
independent on JBossWS security handler.
Please consider unifying the configuration and JBossWS facility use.
Morever check the WSSecurityInfoExtractor if there is also a way to use JBossWS functions
instead of Smooks parsing.
--
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