Releases: phax/phoss-smp
Releases · phax/phoss-smp
phoss SMP 5.3.1
- If the DB connection is lost during a run, it can now be re-established via the GUI
- Fixed a concurrency issue when using the SQL backend
phoss SMP 5.3.0
Ensure to read https://github.com/phax/phoss-smp/wiki/Migrations before upgrade
- Updated the list of known identifiers to Peppol Code list 7.2
- The SQL backend was changed to use JPA to JDBC
- The SQL backend now supports FlyWay for easy DB migrations
- For the SQL backend the special table "smp_user" is migrated to internal users and the ownership is updated.
- Added the possibility to initially setup the database using FlyWay
- Changed the license of the
phoss-smp-backend-sql
module to Apache 2.0 because nothing of the original source code is left - Dropped the support for the specific DB user management - only the build-in user management can be used
- Added support for a query API (see issue #145). To use this functionality, the new configuration item
smp.rest.remote.queryapi.disabled
must be set tofalse
. - Fixed a bug in the Bulk Certificate Change functionality regarding the formatting of certificates
- Changed the JAXB generated classes to use Java 8 date time classes
- Added new Status item
smp.sql.target-database
for SQL backends - Added new configuration item
jdbc.schema
to make the JDBC Schema name customizable - Added new configuration item
jdbc.schema-create
to customize whether the DB schema should be automatically created for an empty database or not - Updating to the latest Directory software includes a change in the resolution of configuration files. See the Migrations page for details.
- When registering the SMP to the SML, it can now be done using "https" addresses (when not in Peppol mode)
phoss SMP 5.3.0 Release Candidate 6
- Added new configuration item
jdbc.schema-create
to customize whether the DB schema should be automatically created for an empty database or not
phoss SMP 5.3.0 Release Candidate 5
- Fixed a bug in the Bulk Certificate Change functionality regarding the formatting of certificates
- Changed the JAXB generated classes to use Java 8 date time classes
- Added new Status item
smp.sql.target-database
for SQL backends - Added new configuration item
jdbc.schema
to make the JDBC Schema name customizable
phoss SMP 5.3.0 Release Candidate 4
- Removed a wrong "UNIQUE" statement from the PostgreSQL init script
phoss SMP 5.3.0 Release Candidate 3
- Fixed a bug in a DELETE SQL statement for endpoints
phoss SMP 5.3.0 Release Candidate 2
- Added the possibility to initially setup the database using FlyWay
- Changed the license of the
phoss-smp-backend-sql
module to Apache 2.0 because nothing of the original source code is left - Dropped the support for the specific DB user management - only the build-in user management can be used
- Added support for a query API (see issue #145). To use this functionality, the new configuration item
smp.rest.remote.queryapi.disabled
must be set tofalse
.
phoss SMP 5.2.6
- The initialization of the UTC timezone upon startup is now more consistent
- Fixed an error that prevented the automatic deletion of Business Card when a Service Group was deleted (see issue #139)
- Improved logging on actions on Business Cards
- Fixed a rare scenario where it would have been possible to create invalid XML in querying
- Fixed an Exception with the MongoDB backend, if a process had no endpoints
- Made separate pages for "Import" and "Export" of Service Groups
- Added possibility to disable support for the HTTP OPTIONS verb (see issue #142)
- Added support for the Content Security Policy (CSP) response headers (see issue #141)
- Added possibility to remove the authorship text from the public page (see issue #140)
- The server name on the start page now uses the same algorithm for calculation as the "list servicegroup" API
- The bulk change certificate page now has an improved certificate matching algorithm (see issue #143)
- The bulk change operations (endpoint and certificate) are now running asynchronously in the background
phoss SMP 5.3.0 Release Candidate 1
- Updated the list of known identifiers to Peppol Code list 7.2
- The SQL backend was changed to use JPA to JDBC
- The SQL backend now supports FlyWay for easy DB migrations
- For the SQL backend the special table "smp_user" is migrated to internal users and the ownership is updated.
phoss SMP 5.2.5
- Fixed a regression that prohibited the creation of ServiceGroups in the SMLs, due to a bogus SoapAction (see issue #137)