As a Developer I want to update our signing and verification process so that verification of ASIC-E containers succeeds for both batched and non-batched signing

 When batch signing is disabled ASiC-E container cannot be successfully validated as message XADeS-B signature references whole payload (including attachments).

We have a pre-existing PR that adds non-batch signing support, but it currently does not resolve the issues with ASIC-E container verification: https://github.com/nordic-institute/X-Road/pull/2219/files

Acceptance criteria:

• Non-batch signing support is added, there is no need to be able to enable it for X-Road 7, but the implementation should be aware of when non-batch signing is used and log all message parts in that case

  • If batch signature is used, only the required message parts are logged (just like in versions < 7.6.0)

• ASIC-E container verification for both batch signing and non-batch signing works

• ASIC-E container verification works with different message types:

  • REST

  • SOAP

  • SOAP with attachments

  • SOAP + MTOM payload

• ASIC containers are created for all logging levels (even if only full body logging will create correctly verifiable archives)

• Data exchange between two Security Servers that use different signature configuration (batch signature vs non-batch signature) works, messages are logged to message log database, ASIC containers are created and they can be verified.

• Automated tests are added to make sure it works as intended