As far as I can tell if I use a custom keystore/truststore location, it should update this block in my CalculatorWSService.xml.
<wsp:Policy wsu:Id="CalculatorWSPortBindingPolicy">
<wsp:ExactlyOne>
<wsp:All>
<sc:CallbackHandlerConfiguration wspp:visibility="private">
<sc:CallbackHandler default="wsitUser" name="usernameHandler"/>
<sc:CallbackHandler default="changeit" name="passwordHandler"/>
</sc:CallbackHandlerConfiguration>
<sc:TrustStore wspp:visibility="private" peeralias="xws-security-server"/>
<sc:KeyStore wspp:visibility="private" alias="xws-security-client"/>
</wsp:All>
</wsp:ExactlyOne>
</wsp:Policy>
But it appears not to do so. I can custom add the fields as it would look if it has done so based upon what I have seen in the Using WSIT Security text you recommended. Like so. But when I run my standalone client, I get the same error.
<wsp:Policy wsu:Id="CalculatorWSPortBindingPolicy">
<wsp:ExactlyOne>
<wsp:All>
<sc:CallbackHandlerConfiguration wspp:visibility="private">
<sc:CallbackHandler default="wsitUser" name="usernameHandler"/>
<sc:CallbackHandler default="changeit" name="passwordHandler"/>
</sc:CallbackHandlerConfiguration>
<sc:TrustStore wspp:visibility="private" peeralias="xws-security-server" location="/Users/douglas/SDDAG_Installs/gf/glassfish/domains/domain1/config/cacerts.jks" storepass="changeit" />
<sc:KeyStore wspp:visibility="private" alias="xws-security-client" location="/Users/douglas/SDDAG_Installs/gf/glassfish/domains/domain1/config/keystore.jks" storepass="changeit" />
</wsp:All>
</wsp:ExactlyOne>
</wsp:Policy>
Any ideas?
Also, in the WSIT manual page 103/4 it specifies that the client keystore should use alias xws-security-client and the truststore should use xms-security-server, but once these have been changed into alias and peeralias in the <wsp:All> block they are both xws-security-server. Is that a bug or am I just not understanding that? Cheers.
[Message sent by forum member 'dpwr' (dpwr)]
http://forums.java.net/jive/thread.jspa?messageID=242720