v4.8.4

• The rejection of a pushed incoming UserMessage on leg 1 with an invalid RFC 2822 eb:MessageId with EBMS:0009 that was added in v4.8.3 can now be disabled, because senders in production environments do not always adhere to the rules.
  Use the new configuration property phase4.incoming.strict.messageids (default true) for this, and AS4Configuration.isIncomingStrictMessageIDs() was added.
  If it is disabled, these messages only lead to a warning, like all other incoming cases.
  Whitespace-only values are included in this.
  The checks of outgoing eb:MessageId values are not affected and always apply.
  See #413
• An invalid refToMessageID set on a sender builder no longer makes isEveryRequiredFieldSet() fail, because the referenced ID may stem from a received message and is not under the control of the sender.
  The value is sent unchanged with a warning.
• An incoming message is now rejected with EBMS:0102 if a decrypted attachment cannot be written to its temporary file.
  Before, this was only logged and the incomplete file was used.
  This also applied to a failed AEAD authentication tag check, which was only found at that point and ended with an HTTP 500 response.
• IAS4IncomingMessageState.getDecryptingCertificateReferenceType() now returns the reference type of the encrypted key.
  Before, it wrongly returned the one of the signature.
• (Peppol) As a consequence, the check that the decrypting certificate is provided as a BinarySecurityToken now really tests the encryption, as required by section 4.7 of the Peppol AS4 profile.
  So far it tested the signature instead.
  Messages using another key identifier type for the encryption are now rejected with EBMS:0103.
  Setting phase4.peppol.inbound.reject-on-non-compliance to false turns this into a logged error.
• (Peppol) An incoming message with more than one attachment is now rejected with EBMS:0004, before any attachment is read.
  Before, the additional attachments were read, ignored, and a Receipt was returned.
  The Peppol AS4 profile requires the SBDH in the first MIME attachment and the Peppol Business Message Envelope specification requires every payload to be wrapped in an SBDH, which leaves room for exactly one payload.
  Setting phase4.peppol.inbound.reject-on-non-compliance to false turns this into a logged error as well.
• (HR eDelivery, DBNAlliance) An incoming message with more than one attachment is now rejected with EBMS:0004, before any attachment is read.
  Before, the additional attachments were read, ignored, and a Receipt was returned.

What's Changed

• Property for enabling new checks from #412 by @beth-soptim in #413

Full Changelog: phase4-parent-pom-4.8.3...phase4-parent-pom-4.8.4