Wednesday, 2 May 2018

Keycloak 4.0.0.Beta2 released

To download the release go to the Keycloak homepage.

Highlights


Pushed Claims

With pushed claims it is now possible for clients to push additional claims to have them used by policies when evaluating permissions.

Resource Attributes

It is now possible to define attributes on resources in order to have them used by policies when evaluating permissions.

Spring Boot 2 support

We now have support for Spring Boot 2.

Instagram identity provider

Thanks to hguerrero it is now easy to enable login with Instagram.

Slovak translation

Thanks to Joe32 we now have Slovak translations.

More...

The full list of resolved issues is available in JIRA.

Upgrading

Before you upgrade remember to backup your database and check the upgrade guide for anything that may have changed.

3 comments:

  1. I am very excited about the Spring Boot 2 support, but have no idea how to use it. Unfortunately the Keycloak documentation does not cover the Spring Boot 2 adapter yet. Does anyone know of an example project, article etc that I can refer to in order to figure out how to use the Spring Boot 2 support?

    I currently have a Spring Boot 1.5 project secured using the Keycloak Spring Boot (1) adapter. The Spring Boot project exposes a REST service which is secured by a Keycloak bearer-only client. The project also has a Springfox Swagger user interface that obtains an access token using a Keycloak public client. The access token obtained via the public client is then presented to the REST service. I want to upgrade this project to Spring Boot 2 with the new Spring Boot 2 Keycloak adapter, but don't know how to use it. My sample project can be found at:
    https://github.com/binary-paper/invoice-service

    ReplyDelete
  2. Follow the instructions for Spring Boot here - https://www.keycloak.org/docs/latest/securing_apps/index.html#_spring_boot_adapter

    but instead of keycloak-spring-boot-starter use keycloak-spring-boot-2-starter.

    I have only done a very basic test that this starts and require authentication for the secured endpoint.

    ReplyDelete
  3. I cannot thank you enough for the help.

    All I had to do was update the Spring Boot version to 2.0.1.RELEASE and the Keycloak version to 4.0.0.Beta2. I also changed the keycloak-spring-boot-starter dependency to keycloak-spring-boot-2-starter. No canges outside of the Maven POM file were required.

    With this being so easy, I think the updated to the official Keycloak documentation will be really easy to do and require minimal changes.

    ReplyDelete

Please only add comments directly associated with the post. For general questions use the Keycloak user mailing list.