Releases: telefonicaid/fiware-keypass
Releases · telefonicaid/fiware-keypass
1.12.0
1.11.0
What's Changed
- UPGRADE: testng dep from 6.1.1 to 7.7.0
- UPGRADE: HSQLDB from 2.2.9 to 2.7.1
- UPGRADE: Java from 8 to 17 in Dockerfile
- UPGRADE: lxml from 4.6.5 to 4.9.1.
- UPGRADE: java mysql connector from 8.0.27 to 8.0.28
- UPGRADE: Debian version from 11.2 to 12.4 in Dockerfile
Full Changelog: 1.10.0...1.11.0
1.10.0
What's Changed
- UPGRADE: Dockerfile base image from centos7.9.2009 to Debian 11.2-slim
Full Changelog: 1.9.0...1.10.0
1.9.0
What's Changed
- ADD: Docker healthcheck for keypass API
- FIX: Remove warn about jdbc class driver
- ADD: Minimize Reconnection problems to MySQL servers (#154)
- ADD: upgrade java mysql connector from 8.0.16 to 8.0.27
- ADD: upgrade wso2 balana dep from 1.0.0_wso2v7 to 1.0.3
- ADD: replace travis by gitactions
- Remove trusty dist from travis (including oraclejdk)
- FIX: upgrade lxml test behaviour dep from 4.6.2 to 4.6.3 due to vulnerability
1.8.0
What's Changed
- Upgrade Dockerfile base image from centos7.7.1908 to centos7.9.2009
- ADD: env var to set db user and password in docker entry point (#142)
Full Changelog: 1.7.0...1.8.0
1.7.0
What's Changed
- ADD: Fix serverTimezone to UTC in mysql jdbc driver uri
- ADD: upgrade java mysql connector from 5.1.49 to 8.0.16
Full Changelog: 1.6.0...1.7.0
1.6.0
What's Changed
- ADD: fix Centos 7.7.1908 version in dockerfile
- ADD: Fix net.sf.ehcache.skipUpdateCheck (#136)
- ADD: upgrade java mysql connector from 5.1.47 to 5.1.49
- ADD: fix /opt/keypass directory to 1000 user for docker
- ADD: autoReconnect to jdbc url configuration (#116)
- ADD: disable usage of SSL for mysql in jdbc url configuration (#126)
- ADD: env var to set log level in docker entry point
- Disable log to file in docker
- ADD: allow usage of env vars in docker entry point
Full Changelog: 1.5.0...1.6.0
Tenant header and performance improvements
In this release, the tenant
is extracted from a Header (previously it was part of the REST API).
Additionally, some performance issues were fixed.
First production-ready release
Version 0.2.0 may be considered as the first production-ready release.
It has a complete and stable API, persistence, automated database migrations, a high performance policy per subject cache, daemon scripts and RPM packaging, behavior testing, and a documented troubleshooting manual with user and machine friendly logs.