Security: web services on WLS 8.5, ALSB and proxy on 9.1

Question

Hi everyone, here's my current situation. I've got some web services running on WLS 8.5, and I've imported them as Business Services into ALSB. The web services themselves are not secured, but I modified the WSDLs so that I could create proxy services which enforce the security.
The security enforcement works when I test it through ALSB test console. However, now I'm trying to create a client web service to invoke the proxy. The client is being made using Workshop running on 8.5 server.
I can get the client to successfully invoke the proxy with no policies attached. Then I made a proxy with BEA's Auth.xml required for inbound messages. The keystores are identical on both the proxy server and the client server.
<input>
<wsp:Policy>
<wsp:PolicyReference URI="policy:Auth.xml"/>
</wsp:Policy>
<soap:body use="literal"/>
</input>
I imported the WSDL into workshop and created a java control from it. I attached a WSSE policy file to the control:
<wsSecurityOut>
<encryption>
<encryptionKey>
<alias>flcoi1</alias>
</encryptionKey>
</encryption>
</wsSecurityOut>
Added this control into a blank web service. The only error being returned from the server is:
com.bea.control.ServiceControlException: SERVICE FAULT:
Code:java.lang.NullPointerException
String:null
Detail:
END SERVICE FAULT
with no further explanations. Does someone know what would cause this exception? Or if it's even possible to do what I'm trying (between WLS 8 and 9)?

Answer 1

Hi!
In my tries to get security to work between WL 8.x to ALSB I realized that WL 8.x don't have support for WS-Security (and therfore WS-Policy) that ALSB uses, but maybe there are some workarounds...
/Patrik