You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Zsolt Beothy-Elo (JIRA)" <ji...@apache.org> on 2019/02/27 10:06:00 UTC

[jira] [Created] (CXF-7983) JweClientResponseFilter fails to decrypt response, when it has status 204 No Content

Zsolt Beothy-Elo created CXF-7983:
-------------------------------------

             Summary: JweClientResponseFilter fails to decrypt response, when it has status 204 No Content
                 Key: CXF-7983
                 URL: https://issues.apache.org/jira/browse/CXF-7983
             Project: CXF
          Issue Type: Bug
          Components: JAX-RS Security
    Affects Versions: 3.3.0, 3.2.4
            Reporter: Zsolt Beothy-Elo
         Attachments: encryption-exception.zip, test-output.txt

JweClientResponseFilter fails to decrypt response, when it has status 204 No Content
For my current project I am trying to get familiar with the cxf JOSE framework. Currently I am running into a problem with JWE trying to encrypt request and response with compact serialization. I have a GET request where the response is correctly encrypted and decrypted, and I have a POST request where the response sends status code 204 and the body is obviously empty.
The response fails with a warning "WARNUNG: 5 JWE parts are expected" and an exception
org.apache.cxf.rs.security.jose.jwe.JweException: INVALID_COMPACT_JWE
    at org.apache.cxf.rs.security.jose.jwe.JweCompactConsumer.<init>(JweCompactConsumer.java:40)
    at org.apache.cxf.rs.security.jose.jaxrs.AbstractJweDecryptingFilter.decrypt(AbstractJweDecryptingFilter.java:44)
    at org.apache.cxf.rs.security.jose.jaxrs.JweClientResponseFilter.filter(JweClientResponseFilter.java:42)
...
Test case and test log with exception are attached.
I debugged the code a bit and it seems to me the filter method in JweClientResponseFilter fails to identify the body is empty and therefor calls the decrypt method, which it shouldn't

 

I ran the test case using 3.2.4 and 3.3.0, but also other versions will be affected.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)