Releases: realityforge/gwt-keycloak
Releases · realityforge/gwt-keycloak
v0.14
Changes in this release:
- Remove remaining references on GWT framework.
- Re-add support for Keycloak 5.
v0.13
Changes in this release:
- Update the
org.realityforge.akasha
artifacts to version0.30
. - Move to using jsinterop for javascript interoperability.
v0.12
Changes in this release:
- Upgrade the
org.realityforge.akasha
artifacts to version0.15
.
v0.11
Changes in this release:
- Upgrade the
org.realityforge.akasha
artifact to version0.10
.
v0.10
Changes in this release:
- Upgrade the
au.com.stocksoftware.idea.codestyle
artifact to version1.17
. - Remove infrastructure supporting integration with the historic GWT "events" packages.
- Migrate from using Elemental2 to Akasha when interacting with the Browser API.
v0.9
Changes in this release:
- Change
Keycloak.MIN_TOKEN_VALIDITY_SECONDS
from15s
to60s
. It seems that the skew of the clocks between the browser and the keycloak server can be significant in some scenarios. Increasing the minimum time decreases the chance that the skew could cause an expired token to be used by the client and rejected by the server. This does increase the number of validations and re-requests that can occur but the additional safety is considered an acceptable tradeoff.
v0.8
Changes in this release:
- Remove some duplicate code when preparing login.
- Remove unused class
NullKeycloakListener
. - Avoid sharing
actions
cache betweenKeycloak
instances.
v0.7
Changes in this release:
- Specify a
Keycloak.MIN_TOKEN_VALIDITY_SECONDS
that has a reasonable default for minimum validity and changeKeycloak.updateToken(Runnable)
to use default value rather than0
. - Add
Keycloak.updateTokenAndExecute(Runnable)
override that usesKeycloak.MIN_TOKEN_VALIDITY_SECONDS
for minimum validity time.
v0.6
Changes in this release:
- Backport
Keycloak.updateTokenAndExecute(...)
which was implemented in some variation for every downstream project.