v0.17.0

Bugfixes

• the logout endpoint now also supports POST requests (#173)
• requests to realms other than the default one are now supported again when not using the default context path /auth
  • when introducing support for different context paths, one hard-coded usage of /auth has been overlooked before

Removed functionality

• the endpoint [/auth]/realms/:realm/protocol/openid-connect/delegated has been removed
  • this functionality has been dropped in Keycloak with version 16, see keycloak/keycloak#9106

v0.16.0

New features

• it is now possible to set the token lifespan in ServerConfig, TokenConfig or via CLI option (thanks @Akvel for the idea and PR #150 )
• it is now possible to set the scopes of the token via CLI option

Changed behavior
To make it consistent with the rest of the API, default scopes defined in ServerConfig are now no longer appended to those in the TokenConfig. Instead, if scopes are defined in TokenConfig, they replace any default scopes defined in ServerConfig.

v0.15.2

Bugfixes

• the generated JWT did not contain header fields "typ" or "alg" (#148)

v0.15.1

Bugfixes

• base64 encoding of provided signing key was wrong (#144, thanks @nbaars for the PR)

v0.15.0

New features

• configure context path for Keycloak 18+ compatility (#126, thanks @kilmajster for the PR)

v0.14.0

New features

• support OpenID Connect RP-Initiated Logout (#137)
• support generating proper name and email values from subject / login name (#140)

v0.13.0

New features

• allow setting default scopes in server configuration (#128, thanks @mdanish98 for the PR)

v0.12.0

Bugfixes

• update to vert.x 4.3 to fix #122
  • ⚠️ Important: This new version will not run with Spring Boot < 2.6.4 if you use Spring's BOM. In this case, stay at version 0.11.0, it is otherwise identical to 0.12.0.

v0.11.0

Bugfixes

• support form-based authentication for confidential clients (#98), thanks to @marcelocamanho for the patch
• support restarting of the mock (#101)

v0.10.0

Bugfixes

• fill the token_type field in the token response (#95), thanks to @wyfrel for the patch