phax/phoss-smp phoss-smp-parent-pom-8.2.0

v8.2.0

on GitHub

• The management UI was migrated from Bootstrap 4 to Bootstrap 5 (5.3.8), using the new ph-oton-bootstrap5 0.9.2 library instead of ph-oton-bootstrap4 10.2.0.
  This is a change of the UI layer only - neither the REST API, nor the data models, nor the semantics of any configuration property were changed by it.
  Note: if you use the configuration property webapp.imprint.cssclasses, the values must now be Bootstrap 5 CSS class names - e.g. badge text-bg-primary instead of the Bootstrap 4 badge badge-primary. See [[Configuration]] for details.
  See #511
• The REST API no longer reveals whether a specific user exists or not, when the authentication fails.
  All authentication failures (unknown user, deleted user, invalid password, disabled user, unknown or deleted Bearer token) can now return the same generic error message, controlled by the new configuration property smp.rest.auth.errordetails.
  For backwards compatibility it defaults to true (detailed messages) - for security reasons it should be set to false. The detailed reason is always logged on the server, independent of this setting.
  Added the new constant SMPUserManagerPhoton.MSG_AUTH_FAILED and the new constructor SMPUnknownUserException (String, String) taking an explicit error message.
  See #510 - thx @jehon
• Bearer tokens are no longer written to the log file and are no longer part of the HTTP error responses of failed REST API authentications - only a shortened representation is used
• Fixed that ISMPProcess.getEndpointCount () returned the number of used Transport Profiles instead of the total number of contained Endpoints.
  If a Process contained multiple Endpoints with the same Transport Profile, the returned count was too low.
  See #498 - thx @gregjotau
• Fixed that ISMPProcess.getAllEndpointsOfTransportProfile (...) returned null instead of an empty list, if the provided Transport Profile ID was null or empty, violating the non-null contract of the method.
  See #499 - thx @gregjotau
• (Docker) All maintained Docker images now use tomcat:10.1-jdk25 as the runtime baseline (was JDK 21). The Java source and target compatibility remains at Java 17.
  See #496 - thx @gregjotau
• (Docker) Fixed the build stage of Dockerfile-release-from-source-xml that still used an obsolete Java 11 based toolchain - it now uses maven:3.9-eclipse-temurin-17.
  See #497 - thx @gregjotau
• (Docker) Fixed that CATALINA_OPTS was appended to before it was initialized, leading to a build warning and to the loss of the entropy option when the memory options were added.
  See #500 - thx @gregjotau
• (Docker) All Docker images that don't compile Java inside the container now use the JRE-only tomcat:10.1-jre25 runtime baseline instead of tomcat:10.1-jdk25, making the images roughly 20% smaller.
  Only the Dockerfile-snapshot-from-source-* files, that build phoss SMP from source inside the image, keep the JDK based baseline.
  See #508 - thx @gregjotau
• (Docker) The build stage of Dockerfile-release-from-source-xml now uses maven:3.9-eclipse-temurin-25 instead of maven:3.9-eclipse-temurin-17. The Java source and target compatibility remains at Java 17.

What's Changed

• Fix release-from-source Docker toolchain by @gregjotau in #502
• Initialize CATALINA_OPTS before appending Docker options by @gregjotau in #505
• Run maintained Docker images on JDK 25 by @gregjotau in #501
• Count all endpoints in SMPProcess by @gregjotau in #503
• Honor the non-null endpoint-list lookup contract by @gregjotau in #504
• Enable native access for Tomcat on JDK 25 by @gregjotau in #507
• Use JRE 25 for release Docker images by @gregjotau in #509
• Bootstrap 5 UI by @phax in #511

New Contributors

• @gregjotau made their first contribution in #502

Full Changelog: phoss-smp-parent-pom-8.1.8...phoss-smp-parent-pom-8.2.0