on 01-25-2021 4:30 AM
Hi ,
We are working on a PROXY to SOAP scenario which has a 2 way authentication requirement.
If we use a SOAP adaptor at receiver side, with certificate authentication with sender certificate , security profile as Web services security and hardcode some static soap header using the module AddSOAPHeaderBean module, the scenario works fine.
But since we require dynamic header values , we want to configure the exact same setup using SOAP AXIS protocol . The configuration works fine from sending the request perspective as the target system is getting the request properly and sending a response back as well.
But the message is failing in the response handler with error com.sap.engine.interfaces.messaging.api.exception.MessagingException: WSDoAllReceiver: security processing failed; nested exception is:
org.apache.ws.security.WSSecurityException: The signature or decryption was invalid
Not sure what are the parameters to maintain for this handler to make it work same as a normal soap scenario that works.
Im currently maintaining the public certificate of the target as user (tried * also), and action as Signature, password as blank.(referring to the sample available in AXIS FAQ note)
Can any one suggest possible solutions /fixes for this issue?
User | Count |
---|---|
82 | |
11 | |
10 | |
8 | |
6 | |
6 | |
6 | |
6 | |
5 | |
5 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.