Hi,
I just starting working on WSS4J.. I am doing this effort to test
interop with oracle's OWSM.
I want to know how to avoid EmbeddedKey in response (and also don't
understand why is it required to encrypt key in response as it should be
only required in request flow)
I have OWSM's client policy for symmetric key sign and encrypt (wss11)
, this request goes to Axis service which has WSS4J policy... request
goes fine and response is signed and encrypted by wss4j but response is
not understood by OWSM as response has EncryptedKey in soap message
which owsm doesn't expect.
I don't understand the need of having EncryptedKey in response and want
to avoid it.. wss4j should just sign and encypt and shouldn't encrypt
key. I also don't understand how is it encrypting key at server side as
it is not having client's public key.
this is service.wsdd file
<requestFlow>
<handler type="java:org.apache.ws.axis.security.WSDoAllReceiver">
<parameter name="passwordCallbackClass"
value="PWCallback1"/>
<parameter name="action" value="Signature Encrypt"/>
<parameter name="signaturePropFile"
value="crypto.properties" />
<parameter name="decryptionPropFile"
value="crypto.properties" />
<parameter name="encryptionKeyIdentifier"
value="DirectReference" />
<parameter name="decryptionKeyIdentifier"
value="DirectReference" />
<parameter name="signatureKeyIdentifier"
value="DirectReference" />
</handler>
</requestFlow>
<responseFlow>
<handler type="java:org.apache.ws.axis.security.WSDoAllSender" >
<parameter name="passwordCallbackClass"
value="PWCallback1"/>
<parameter name="user" value="orakey"/>
<parameter name="action" value="Signature Encrypt"/>
<parameter name="signaturePropFile"
value="crypto.properties" />
<parameter name="signatureKeyIdentifier"
value="DirectReference" />
<parameter name="encryptionKeyIdentifier"
value="Thumbprint" />
</handler>
</responseFlow>
I have tried many other options too but didn't work
Thanks
Nitin
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
