Releases: phax/phoss-directory
Releases · phax/phoss-directory
phoss Directory 0.11.0
- Updated to Lucene 8.x
phoss Directory 0.10.5
- Improved logging of indexation
- SMP client configuration became more resilient
Full Changelog: phoss-directory-parent-pom-0.10.4...phoss-directory-parent-pom-0.10.5
phoss Directory 0.10.4
- Added new configuration parameter
smp.tls.trust-all
to disable the TLS certificate checks for the SMP client
Full Changelog: phoss-directory-parent-pom-0.10.3...phoss-directory-parent-pom-0.10.4
phoss Directory 0.10.3
- Updated to Apache Http Client v5.x
- Updated to ph-web 9.7.1
- Fixed an error in the REST API with the "name" parameter when multilingual names are used
Full Changelog: phoss-directory-parent-pom-0.10.2...phoss-directory-parent-pom-0.10.3
phoss Directory 0.10.2
- Removed the code for the handling of objects marked as deleted
- Improved the owner check upon deletion
phoss Directory 0.10.1
- Added export of participant IDs with metadata
phoss Directory 0.10.0
- Only the SP owning a Participant can delete it. That implies, that upon certificate change the simple deletion will not work. It is recommended to first index the participant, so that the new certificate is used, and than delete it with the new certificate.
- Added an Admin page to manually delete a participant without an owner check
- Showing metadata information on participant details, if the admin user is logged in
- Removed the "SMP implementations" page
- Added a possibility to hide or customize the "Contact us" page
- Changed the PD Client configuration properties, to start with
pdclient.
and align the HTTP properties with SMP client configuration - Fixed the default search background image URL
phoss Directory 0.9.10
- Prepare for internal cleanup to get rid of the legacy "deleted" flag
phoss Directory 0.9.9
- Updated to Log4J 2.17.0 because of CVE-2021-45105 - see https://logging.apache.org/log4j/2.x/security.html
phoss Directory 0.9.8
- Updated to Log4J 2.16.0 because of CVE-2021-45046 - see https://www.lunasec.io/docs/blog/log4j-zero-day/