E1: BSSV: Build and deploy causes Security Policy change with new Tools 188.8.131.52 and above with WLS 10.3.6
Last updated on MAY 01, 2014
Applies to:JD Edwards EnterpriseOne Tools - Version 9.1 and later
Information in this document applies to any platform.
Using E1 9.1 with Tools 184.108.40.206 and WLS 10.3.6 with a JAX-WS Package. (Also happens with WLS 10.3.5 with Tools Release 9.1.4.x and JAX-WS)
Just upgraded the E1 tools from 220.127.116.11 to 18.104.22.168 and now the new bssv wsdl has a bssvpolicy for the security. This is not allowing to pass user name and password via https from Oracle SOA Suite BPEL services. Is there a reason this changed? How can the bssv service be built with the original security policy policy:Wssp1.2-2007-Https-UsernameToken-Plain.xml?
Looks like the BSSV build process is causing the wsdl to be created with the bssvpolicy.xml instead of the old policy.
Here is the error message from the SOA BPEL process when invoking the new wsdl:
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms