Hi Ted,

No need to change the phase order. Sandesha2 will treat Security phase as
special and will be calling it in each retransmission (for things like
Tamstamp to be updated).

Please attach your client and service code to the JIRA. I'll try to
reproduce the error.

Chamikara



On 6/13/07, Ted Jones <[EMAIL PROTECTED]> wrote:

 Chamikara,

Thanks for the reply. I reset the SecurityManager to the dummy and I am
now getting this:


2007-06-13 10:42:12,703 ERROR org.apache.sandesha2.workers.SenderWorker -
Sandesha2 got an exception when sending a message:
org.apache.axis2.AxisFault: WSDoAllSender: Empty username for specified
action.

org.apache.axis2.AxisFault: WSDoAllSender: Empty username for specified
action

at org.apache.rampart.handler.WSDoAllSender.processMessage(
*WSDoAllSender.java:94*)

at org.apache.rampart.handler.WSDoAllHandler.invoke(
*WSDoAllHandler.java:72*)

at org.apache.axis2.engine.Phase.invoke(
*Phase.java:383*)

at org.apache.axis2.engine.AxisEngine.invoke(
*AxisEngine.java:203*)

at org.apache.axis2.engine.AxisEngine.resumeSend(
*AxisEngine.java:318*)

at org.apache.sandesha2.workers.SenderWorker.run(
*SenderWorker.java:258*)

at
edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask
(
*ThreadPoolExecutor.java:665*)

at
edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run
(
*ThreadPoolExecutor.java:690*)

at java.lang.Thread.run(
*Thread.java:534*)
When using Rampart UsernameToken security with Sandesha2, does the phase
order need to change? Perhaps the WS-Security headers need to be added prior
to the RM phase? I will log a JIRA (assuming it is not just a user error).

FYI - I switched to HTTP Basic security with Sandesha2 and it worked fine.

Thanks again,
Ted



 ------------------------------
*From:* Chamikara Jayalath [mailto:[EMAIL PROTECTED]
*Sent:* Tuesday, June 12, 2007 11:34 PM
*To:* [email protected]
*Subject:* Re: [Axis2] Sandesha2 1.2 plus Rampart 1.2 in Axis2 1.2

Hi Ted,

You do not need the SecurityManager in Non-SecureConversation scenarios.
Can u please try without that.  Also it will be helpful if you can raise a
JIRA and attach ur client code, the error logs etc.

Chamikara


On 6/13/07, Ted Jones <[EMAIL PROTECTED]> wrote:
>
>  I am able to use Rampart 1.2 (UsernameToken) and Sandesha2 1.2 in Axis2
> 1.2 as standalone modules, but when I engage them both I do not see any
> messages in TCPMon and my client times out before I get a response. I
> updated the Sandesha2.mar module.xml Security Manager to use
> org.apache.sandesha2.security.rampart.RampartBasedSecurityManager. Are
> there any steps I am missing?
>
> (I apologize if this is the wrong group for this posting. If so, kindly
> point me to the correct forum.)
>
> Thanks,
> Ted
>



--
Chamikara Jayalath
WSO2 Inc.
http://wso2.com/
http://wso2.org/ - For your Oxygen needs




--
Chamikara Jayalath
WSO2 Inc.
http://wso2.com/
http://wso2.org/ - For your Oxygen needs

Reply via email to