Hi,
I've got a Axis2 1.1 (using Rampart 1.1) client that needs to talk with a .NET
WSE service and a JAX-WS service. I can't get the Axis2 client to work with
both services at the same time because of the order of the security actions.
If I specify in the rampart security config:
<parameter name="InflowSecurity">
<action>
<items>Timestamp Signature Encrypt</items> ....
then the Axis2 client complains about the WSE response because the order in
its response's security header is timestamp, encryption and signature. The
error message is: "WSDoAllReceiver: security processing failed (actions
mismatch)". (Axis2 is fine with the JAX-WS response, which has the order as
encryption, signature and timestamp.) Unfortunately, the WSE service can't be
changed because it doesn't have the configuration functionality to change the
position of the timestamp (only signing and encrypting).
If I change the order in the rampart security config to:
<items>Signature Encrypt Timestamp</items>
then the Axis2 client is fine with the WSE response, but it is unhappy with
the JAX-WS response (It's the same error message as before). Unfortunately, the
JAX-WS service can't be changed because when the timestamp is placed after
signing in the JAX-WS config, then the timestamp can't be signed.
So how do I configure on the Axis2 client to not care about the order of the
security actions? Ideally I want it to not care what security actions there
are in the responses, but if a security action, e.g. sign, encrypt, is done,
then it will verify the security action.
Thanks in advance.
Richard
____________________________________________________________________________________
Cheap talk?
Check out Yahoo! Messenger's low PC-to-Phone call rates.
http://voice.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
