phax/phoss-smp phoss-smp-parent-pom-8.7.1

v8.7.1

on GitHub

• The Tasks/Problems page no longer warns about a non-standard transport profile if the transport profile is configured in Administration > Transport Profiles.
• Fixed the nice name display of PINT exact match document types (e.g. urn:peppol:pint:billing-1@om-1).
  Only the PINT wildcard match variant (with *) was recognised, because the nice names read from the mapping XML file were stored in the wildcard form only.
• (SQL) Added the configuration property jdbc.pooling.min-connections to configure the initial and the minimum idle number of pooled database connections.
  The default stays at 4.
  The value is also emitted as the new status item smp.sql.pooling.min-connections.
  Thanks to @tborlee for the contribution to ph-db.
• An outbound participant migration that is already in progress can now be restarted with a new migration key.
  The REST API PUT /migration/outbound/start/{ServiceGroupId} accepts the new query parameter renew=true, and the Migrate to another SMP page has a new "generate new migration key" action.
  The SML replaces the pending key, so the previous key becomes invalid and the local migration record is replaced.
  See #590.
• Fixed the internal error on the Business Cards page when using "Update participant in Directory" or "Update all participants in Directory" with an incomplete PD client configuration (e.g. missing pdclient.keystore.type).
  The page now shows the "Failed to create the Directory client component" error including the technical details.
  PDClientProvider.getPDClient () now throws the new checked PDClientCreationException if the client cannot be created, and the new getPDClientOrNull () logs the problem and returns null.
  The automatic Directory update, the XML import and the REST API POST /businesscard/{ServiceGroupId}/push use the latter and no longer fail with a NullPointerException; the push API returns HTTP 412 instead.
  See #589.
• Fixed the internal error on the Business Cards page when using "Update participant in Directory" or "Update all participants in Directory" with an incomplete PD client configuration (e.g. missing pdclient.keystore.type).
  The page now shows the "Failed to create the Directory client component" error including the technical details.
  See #589.
• The management GUI now uses Bootstrap 5.3.9
• An existing but empty (0 byte) XML data file is now treated like a missing file and re-initialised, instead of preventing the startup
• Hardened the file upload handling (e.g. the Service Group import): an endless loop with overlong multipart boundaries was fixed, temporary files are reliably deleted and the number of parts per request is limited to 1,000
• TRACE requests are now answered with HTTP 405, errors in asynchronous request processing result in HTTP 500 without exception details, and the values of the Authorization and Cookie headers are no longer logged
• The Remote Query API (/smpquery/*) no longer waits longer than 30 seconds if a queried SMP requests a retry via the HTTP Retry-After response header - in that case no retry happens
• Updated to ph-commons 12.6.0, ph-db 8.5.1, ph-web 11.5.0, ph-oton 10.8.0, ph-oton-bootstrap5 1.0.2, peppol-commons 13.2.2, peppol-shared-ui 0.11.3, Flyway 13.12.1, the MongoDB driver 5.14.0, Jackson 3.3.0, the Oracle JDBC driver 23.26.4.0.0 and the MS SQL JDBC driver 13.6.2

Full Changelog: phoss-smp-parent-pom-8.7.0...phoss-smp-parent-pom-8.7.1