Releases: europeana/apikey
Releases · europeana/apikey
Version 1.6
- EA-3798 Updated dependencies, fixed vulnerabilities
- Updated to Java 17
- Updated javadoc
Version 1.3
- [✓] REFACTORED to be deployed using Kubernetes
What's Changed
- EA-3231 remove spring error handling by @SrishtiSingh-eu in #48
- EA-3286: Setup k8s deployment by @ikattey in #47
- Origin/master by @P-Ehlert in #49
- EA-3288: Fix production deployment by @ikattey in #50
New Contributors
Full Changelog: apikey-1.2...apikey-1.3
Version 1.2
- FIX handle empty content header properly
- REFACTOR update dependencies
Version 1.1
Updated dependencies and improved logging
Version 1.0
This is the first production release of the Apikey service:
- default behaviour is that Apikeys are created and treated as separate entities (ie. no linked Keycloak Client is created);
- it is possible to create a linked Apikey + Keycloak Client pair or to add a Keycloak Client to an existing Apikey (see the documentation for details). The service will keep administrative actions (deprecation, activation) done on Apikeys synced with linked Clients when applicable;
- administrative access is authenticated with ID and secret of the designated Client except when creating an Apikey using Google Captcha;
- there is no functionality available to delete Keycloak Users;
- for all other details, see the documentation.
(features added since 0.1 Alpha release - note that this list is far from complete):
-
ADD open-up actuator endpoints
-
ADD return keycloakId (when present)
-
ADD logging via Api Commons
-
ADD automatic SSL switch (disabled for local testing)
-
ADD Pingdom checks
-
ADD new Apikey registration form on Pro
-
ADD improved Unit test coverage
-
ADD updated to use Java 11
-
FIX cleaned up Apikey database (unused and deprecated keys)
-
FIX trimmed whitespace when registering new Apikeys
Version 0.1 alpha
First release with keycloak integration