We have a BSSV server running on Weblogic - all according to the MTRs.
We have built a custom Business Function and it is now deployed as a Published Business Service.
I can test this using SOAPUI and adding the wsse:Security headers and the services works perfectly.
Now the problem is that we are trying to proxy the service so that non-SSL enabled clients can call in.
To do this, I have built a proxy service and have it deployed on a separate Weblogic machine (at present, the Integrated server on JDeveloper) in the dev environment.
I have taken the Demo Certs from the BSSV server (also still in the dev environment) and placed them in the "Trust" store on the proxy machine.
Originally there was a hostname lookup error which was overcome by placing the line "set JAVA_OPTIONS=%JAVA_OPTIONS% -Dweblogic.security.SSL.ignoreHostnameVerification=true" into the setDomainEnv file.
The original error has now gone away, but now a new error has appeared. The essence of it is:
java.security.NoSuchAlgorithmException: Algorithm MD5 not available
on the client side, the error given is:
<faultstring>Error on verifying message against security policy Error code:1000</faultstring>
<ns2:exception xmlns:ns2="http://jax-ws.dev.java.net/" class="javax.xml.ws.soap.SOAPFaultException" note="To disable this feature, set com.sun.xml.ws.fault.SOAPFaultBuilder.disableCaptureStackTrace system property to false">
<message>Error on verifying message against security policy Error code:1000</message>
From my understanding, MD5 is used to checksum the keys and compare as part of the SSL handshake.
Can anyone suggest what might be going wrong?
For completeness, I am posing the full error from the BSSV Server log files (193 lines)
--> The message is too long to be posted! I am going to post it in replies to this message now...