Skip to content
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

Add setOptionalSecurementSignatureParts to Wss4jSecurityInterceptor [SWS-1032] #1101

Open
gregturn opened this issue Aug 10, 2018 · 0 comments
Open

Comments

@gregturn
Copy link
Member

@gregturn gregturn commented Aug 10, 2018

Paul Visser opened SWS-1032 and commented

We are building a SOAP client for a service that requires certain elements to be signed. However not all elements will be available in the request at all times.

Wss4j has the option to set optional signature parts (WSHandlerConstants.OPTIONAL_SIGNATURE_PARTS). However Wss4jSecurityInterceptor does not provide a method to set this option.

We are now working around this by setting the option in the messagecontext in a custom interceptor but this is no ideal solution.

As there is a similar issue for another property mentioned in #1093 I would highly recommend to add a possibility to set Wss4j options directly in the handler instead of having to wait for methods to be added to the Spring interceptor. Otherwise I would suggest making the handler protected instead of private so we could extend the interceptor and add such logic there.


Affects: 3.0.3

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant
You can’t perform that action at this time.