Skip to content

Releases: Captain-P-Goldfish/scim-for-keycloak

kc-20-b1

26 Apr 19:50
Compare
Choose a tag to compare
Release to kc-20-b1

kc-19-b1

26 Apr 19:49
Compare
Choose a tag to compare
Release to kc-19-b1

kc-18-b2

24 Sep 09:50
Compare
Choose a tag to compare

Bug Fixes

Release to kc-18-b1

13 Jul 21:53
Compare
Choose a tag to compare

Changes

  • Update deployment to Quarkus keycloak installation
  • Fix usage of SCIM with master-realm

kc-16-b4

26 Mar 12:48
Compare
Choose a tag to compare

Bug Fixes

  • Fixed the problem that the liqubase xml-schema was not found within the resources. The build-server of circle-ci does produce problematic results during build if the xml-schema is set locally so I removed this project from circle-ci build-server.

kc-16-b2

22 Dec 15:33
Compare
Choose a tag to compare

Bug Fixes

  • Added the scim-theme back to its place and added some assertions to prevent such regressions in the future

~~kc-16-b1~~

18 Dec 19:26
Compare
Choose a tag to compare

BROKEN RELEASE

  • I accidentially removed the theme from the sources so this release is in a broken state

Bug Fixes

  • Removed log4j2 dependencies from deployment file. Log4j was packaged within the ear-file but it was not used.

Maintaenance

  • Update base library scim-sdk to version 1.12.3

kc-15-b3

06 Nov 12:16
Compare
Choose a tag to compare

Bug Fixes

  • The user-infinispan-cache was not updated after a user was removed from a group. This caused the groups still to be listed in AccessTokens and the keycloak-web-admin-console eventhough the database was correctly updated.

kc-15-b2

26 Sep 14:06
Compare
Choose a tag to compare

Features

  • update of SCIM-SDK for partial support of MS Azure patch-requests. Refer to the SCIM-SDK release-notes for furhter details
  • the Content-Type header "application/json" will now be accepted and changed to "application/scim+json" before given to the SCIM-SDK execution

Bug Fixes

  • preventing NullPointerExceptions if a user has created timestamp set to null within the database. This should normally not be possible because keycloak is handling this timestamp internally. But if it happens a warning is written into the log

kc-15-b1

11 Sep 09:23
Compare
Choose a tag to compare

Bug Fixes

No source code changes on this side since kc-14-bx is compatible with keycloak 15