Keycloak 2.0.0.Final has just been released. This release only contains some minor fixes since 2.0.0.CR1.
Thursday, 23 June 2016
We're finally back to adding new features. This release is just the beginning and we've planned loads of existing new features in the coming months.
I'm really exited to introduce the authorization services we've just added. Through the authorization services you can centrally define and manage fine-grained permissions for your services. For more details check out the Authorization Services Guide.
There's a brand new website at www.keycloak.org.
Finally we've also completely reworked and significantly improved our documentation.
For nearly 4 years ago Bill Burke and myself started two individual proof of concepts, both focusing on making it easier for developers to securing applications and services. Keycloak was born out of combining these two proof of concepts. There was barely any overlap and the two perfectly complemented each other.
Fast forward to today and we now have a huge community with over 100 contributors and over 400 forks of our Github repository. It's no longer just myself and Bill working on Keycloak, we now have a strong team working on it and I'm very exited about the future of the project.
You may have noticed that lately we've stopped adding new features and focused on improvements and testing. There's a good reason behind that! We've been working on creating a productized and supported version of Keycloak.
I'm extremely pleased to announce that Red Hat now offers a productized and supported version of Keycloak!
For more details on how to get support for Keycloak check out the product pages at https://access.redhat.com/products/red-hat-single-sign-on.
Finally, I'd like to thank everyone that's been involved. All the core developers, quality engineers, others at Red Hat and last but not least our community!
Monday, 13 June 2016
We're now shifting our focus from polish and testing to adding new features, so this will be the last 1.9.x community release. Who knows, maybe that means a product release is around the corner?