Releases: camunda-community-hub/camunda-platform-7-keycloak
Releases · camunda-community-hub/camunda-platform-7-keycloak
Version 7.21.1
Changes in Version 7.21.1:
- New configuration flag
enforceSubgroupsInGroupQuery
for enforcing subgroups in query results when using Keycloak >= 23.0.0
Version 7.21.0
Changes in Version 7.21.0:
- Updated to Camunda Version 7.21.0
Version 7.20.1
Fixes in version 7.20.1:
- Make Camunda Run 7.20.0 Community Edition work again and handle missing
commons-codec
library.
Version 7.20.0
Changes in Version 7.20.0:
- Upgrade to Camunda Platform 7.20.0
- Upgrade to Apache HttpComponents HttpClient 5
- Upgrade to Spring Boot 3.1.x
- Updated samples to Spring Security 6.1
- Upgrade to JDK 17
Special thanks to @cachescrubber for his outstanding help and support throughout the work on this update 🚀.
Version 7.19.0
Changes in Version 7.19.0:
- Updated to Camunda Version 7.19.0
- Updated SSO sample to Keycloak 21.1.1
Hint: this is a re-release of 7.19.0 which originally took place on June 12, 2023 - but artifacts where missing on Maven Central.
Version 7.18.0
Changes in Version 7.18.0:
- Fixed a bug for userId's containing a plus sign.
- Updated samples to Camunda Platform 7.18 and Keycloak >= 18
- Alternative for client side JWT authentication in Camunda Cockpit (incubation status)
Version 7.17.0
Changes in Version 7.17.0:
- Renamed the extension from
camunda-bpm-identity-keycloak
tocamunda-platform-7-keycloak
- Updated samples to Camunda Platform 7.17
- Introduced new version which reflects the Camunda Version used in samples and tests.
Version 2.2.3
New features in version 2.2.3:
- Optional Keycloak Login Cache - helps you to minimize password check requests to Keycloak and thus improve performance. Not applicable in SSO scenarios, but useful e.g. when using External Task Clients with Basic Auth.
Version 2.2.2
Fixes in version 2.2.2:
- Optimized user / group queries when using single items in
userIdIn(...)
/groupIdIn(...)
selections
Version 2.2.1
Fixes in version 2.2.1:
- Fixed bug #73: "like" filters in combination with missing Keycloak attributes (e.g. Keycloak users without email, lastname, firstname) may cause a NullPointerException