Hi all,
Moving to metro 2.4.4 is causing this exception with the same wsit-client configuration
ott 29, 2021 11:18:43 AM com.sun.xml.wss.jaxws.impl.SecurityClientTube processClientResponsePacket
GRAVE: WSSTUBE0025: errore durante la verifica di sicurezza nel messaggio in entrata.
com.sun.xml.wss.XWSSecurityException: Security Requirements not met - No Security header in message
at com.sun.xml.ws.security.opt.impl.incoming.SecurityRecipient.createMessage(SecurityRecipient.java:959)
at com.sun.xml.ws.security.opt.impl.incoming.SecurityRecipient.validateMessage(SecurityRecipient.java:272)
at com.sun.xml.wss.jaxws.impl.SecurityTubeBase.verifyInboundMessage(SecurityTubeBase.java:456)
at com.sun.xml.wss.jaxws.impl.SecurityClientTube.processClientResponsePacket(SecurityClientTube.java:436)
I browsed source code and documentation finding no difference.
I can't understand if it could be a namespace issues (of the wsit file).
This is the simple policy that has been used in both cases.
<wsp:Policy
wsu:Id="PatientIdentityBinding_IssuedTokenForCertificateSecureConversationMutualCertificate11_policyPolicy">
<wsp:ExactlyOne>
<wsp:All>
<sc:TrustStore wspp:visibility="private"
location="store.jks" type="JKS" storepass="thesame"
peeralias="aliastrust"></sc:TrustStore>
<sc:KeyStore wspp:visibility="private"
alias="alias01" keypass="thesame" storepass="thesame"
type="JKS" location="store.jks" />
</wsp:All>
</wsp:ExactlyOne>
</wsp:Policy>
Thanks
Leonardo
|