New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CxfSoapClientIT.wsSecurityClient fails in native mode: wsse:Nonce not present in the request #3966
Comments
It looks like for whatever reason in native mode the |
The |
Also see |
I tried creating a |
I have built github.com/apache/ws-wss4j from source after adding some debug output. The problem seems to be that there is a WSSecurityException swallowed in org.apache.wss4j.dom.message.token.UsernameToken.addNonce(Document) which in turn is caused by a non-initialized secure random in org.apache.xml.security.stax.ext.XMLSecurityConstants of |
Could it be related to this: https://github.com/quarkiverse/quarkus-cxf/blob/master/ws-security/runtime/src/main/java/io/quarkiverse/cxf/graal/CxfWsSecuritySubstitutions.java#L92 I tried to initialize it at the runtime, and I traced the class initialization and here's what I saw:
Not sure how to address this though... |
@ppalaga Good news, we made a slight change in the Quarkus CXF and now all tests pass correctly and nonce is generated properly. What is the next scheduled date for the Camel Quarkus release? We should coordinate the Quarkus CXF release date so that we can update the version and reenable the test in native mode. |
… present in the request apache#3966
Thanks @javaduke , I have a temporary fix for Camel Quarkus. I'd like to check whether the substitutions in quarkus-cxf are really required. They are rather hard to maintain in the long term so other solutions should be preferred. |
… present in the request apache#3966
present in the request apache#3966
present in the request apache#3966
The text was updated successfully, but these errors were encountered: