cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrei Shakirin (Commented) (JIRA)" <>
Subject [jira] [Commented] (CXF-4099) SignedParts, EncryptedParts policy assertions are silently ignored on the client side if specified alone
Date Tue, 14 Feb 2012 12:01:00 GMT


Andrei Shakirin commented on CXF-4099:

Hi Dan and Colm,

OK, now I see the issue with PolicyVerificationOutInterceptor: 
- from one side it should be called late, because it is possible that some interceptors are
invoked on SEND or POST_STREAM phases and they satisfy corresponded policy assertions
- from other side as far as it is called after MessageSenderInterceptor, Conduit already opens
the connection and sets OutputStream into message. It is also possible that message is already
partly sent until PolicyVerificationOutInterceptor is called.
I will follow your suggestion and fix it into PolicyBasedWSS4JOutInterceptor.

But does it make sense to throw exception in PolicyBasedWSS4JOutInterceptor anyway, if assertion
is not satisfied? In some cases message is still not sent, if it is partly send - ok, better
later as never :)
My concern that it is possible to have other, non-security assertions that also can be critical
for client, for example custom compression. If assertion for some reasons is not satisfied
on the client side, why not throw the exception instead send huge uncompressed message? Verify
every individual assertion can be quite complicated.

> SignedParts, EncryptedParts policy assertions are silently ignored on the client side
if specified alone
> --------------------------------------------------------------------------------------------------------
>                 Key: CXF-4099
>                 URL:
>             Project: CXF
>          Issue Type: Bug
>          Components: WS-* Components
>            Reporter: Andrei Shakirin
> Hi,
> Actually if client defines policy containing only SignedParts, EncryptedParts assertions
without binding (Assymetric, Symmetric or Transport) CXF does nothing and send unsigned/unencrypted
message. Exception is thrown only on service side (Assertion is not satisfied). I find it
a little bit dangerous, because client can assume that message is encrypted. IMHO exception
should be thrown already on client side.
> Fix proposals:
> A) PolicyVerificationOutInterceptor 
> As I can see PolicyVerificationOutInterceptor doesn't throw exception in case if policy
assertions are not satisfied.
> That means for outgoing messages (client request and server response) policy assertions
can be not fulfilled and message will be sent anyway.
> Code is below:
> {code:java}
>         // CXF-1849 Log a message at FINE level if policy verification fails
>         // on the outbound-server side of a response
>         try {
>             aim.checkEffectivePolicy(policy.getPolicy());
>         } catch (PolicyException e) {
>             LOG.fine("An exception was thrown when verifying that the effective policy
for "
>                      + "this request was satisfied.  However, this exception will not
result in "
>                      + "a fault.  The exception raised is: "
>                      + e.toString());
>             return;
>         }
>         LOG.fine("Verified policies for outbound message.");
> {code}
> For incoming messages unsatisfied assertion is interpreted as real problem and causes
> I am not sure about the reason of such different verification.
> There are some cases where it can be critical even for outgoing message: encryption,
> B) If alternative A is not possible for some reasons, I would propose to implement additional
interceptor, register it in WSSecurityPolicyInterceptorProvider and check specially for critcal
security assertion satisfaction there. Interceptor should be called after PolicyBasedWSS4J*
> I am going to provide a patch either for A or B.
> Regards,
> Andrei.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message