Added setSecurementEncryptionOptionalParts into Wss4jSecurityInterceptor
Added ability to optionally encrypt XML elements - only when present in the XML
@xscreach Please sign the Contributor License Agreement!
Click here to manually synchronize the status of this Pull Request.
See the FAQ for frequently asked questions.
@xscreach Thank you for signing the Contributor License Agreement!
Fixes #1101
@gregturn sorry for bothering, just want to ask for PR review. And... i haven't noticed the #1101 before i opened the PR, but if you guys would like to change the interceptor a bit differently (e.g. expose the handler field as protected to extending classes), please let me know, i'll update the PR 😉
thanks in advance 🙇♂️
I don't know what the secret is to getting a PR merged but do read over their contributing guidelines :
@xscreach Are you able to fashion a test case using this new feature?
@xscreach Are you able to fashion a test case using this new feature?
Well, not really. We needed it in a company I no longer work for 🤷 IRC the point was to decrypt elements if they were encrypted or use their plain value when not encrypted - optional element de/encryption
Anyway, this PR only allows users to set some configuration for the handler that just wasn't possible before.
Targeting unsupported branch