You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ws.apache.org by "Colm O hEigeartaigh (JIRA)" <ji...@apache.org> on 2011/02/07 13:24:30 UTC
[jira] Closed: (WSS-267) WSDoAllReceiver.invoke not setting proper
WSSConfig on security engine
[ https://issues.apache.org/jira/browse/WSS-267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Colm O hEigeartaigh closed WSS-267.
-----------------------------------
> WSDoAllReceiver.invoke not setting proper WSSConfig on security engine
> ----------------------------------------------------------------------
>
> Key: WSS-267
> URL: https://issues.apache.org/jira/browse/WSS-267
> Project: WSS4J
> Issue Type: Bug
> Components: WSS4J Axis Integration
> Affects Versions: 1.5.10
> Reporter: Brian McDonald
> Assignee: Colm O hEigeartaigh
> Fix For: 1.5.12
>
>
> In WSDoAllReceiver.invoke:164 the security engine is invoked
> wsResult = secEngine.processSecurityHeader
> But the wssconfig is never set so a new wssconfig is created which doesn't have any of the proper confg setting.
> Before that line you need to call
> secEngine.setWssConfig(reqData.getWssConfig());
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ws.apache.org
For additional commands, e-mail: dev-help@ws.apache.org