Axon Data Protection Module
Changelog
4.5.1
• Upgrading Protobuf, Jackson, and Guava libraries to mitigate vulnerabilities.
4.5.0
• Switch from hibernate-jpa-api to jakarta-persistence-api in order to improve Spring Boot 3 and Axon Framework 4.7.0 support
• Update of Axon Framework, Hibernate, Hibernate EM, HSQLDB libraries to improve JDK11+ support
4.1.1
• Update of Protobuf, Jackson and XStream libraries to improve JDK9+ support
• Lenient validation of the license file, to allow for a grace period after expiry
4.1
• Product rename from ‘AxonIQ GDPR Module’ to ‘Axon Data Protection’.
• Version changed to join general Axon platform versioning.
• Package rename from io.axoniq.gdpr to io.axoniq.dataprotection, requiring corresponding changes to applications using the module.
1.4
• Introduced new version compatible with Axon 4.
1.3
• Added support for Scala’s Option type.
1.2
• Added functionality for immediate replacement (see Section 4.2.3).
• Added support for HashiCorp Vault (see Section 4.1.3).
• Enabled placing the license file on the classpath (see Section 2.1).
1.1
• Added support for Scala, including type aliasas for the GDPR Module annotations (see Section 3.7) and support for Scala collections (see Section 3.2).
• Added a JDBC-based CryptoEngine (see Section 4.1).
• Added list of included licenses in this guide, in Appendix B.
1.0.5
• Added functionality for partial and double encryption. See Section 3.2.4 and Section 4.2.2.
1.0.4
• Added functionality to include a preset encryption context in FieldEncrypter#encrypt and #decrypt, to support use cases where there is no field that can serve as @DataSubjectId. (See Section 4.2.1.)
1.0.3
• Corrected handling of null values with @SerializedPersonalData.
• Changed license system property into axoniq.gdpr.license to avoid potential collisions.
• Changed axon-core Maven dependency into optional to avoid the GDPR Module from overriding the project Axon Framework version.
1.0.2
• Corrected typo in manual in Figure 1.
1.0.1
• Corrected handling of primitive types.