Keycloak 1.8.0.CR1 发布 SSO 集成解决方案

Keycloak 1.8.0.CR1 发布，更新如下：

Default Admin User Removed – we no longer have a built in admin account, instead a new account has to be created initially from http://localhost:8080/auth or with the bin/add-user[sh|bat] script
Client Templates – with the introduction of client templates it’s now possible to share mappers and scope configuration between clients
Partial Import – it’s now possible to import users, clients, identity brokers and user federators from a json file into an existing realm
Truststore SPI – we’ve introduced a Truststore SPI which provides a centralized place to manage the truststore for clients, email, user federation and identity brokering
Password Hashing SPI – if you want to import existing users into Keycloak you can implement a password hashing provider so existing hashed passwords can be used (thanks totsudo for the contribution)
Identity Brokering Login Flow – this allows customizing the flow used when a user logs in through an identity broker
SAML v2 Enhanced Client or Proxy Profile (ECP) – this SAML profile is useful for non-browser based clients (for example a desktop application)
OAuth2 Token Introspection – the OAuth2 token introspection specification provides a standard way to obtain the active state of a token
Conditional OTP – requiring OTP used to be either enabled or disabled for a realm, it’s now possible to conditionally choose which users require OTP based on for example a role or a request header (thanks to thomasdarimont for the contribution)
Realm Display Name – a display name has been added to realms, which makes it possible to set a human readable name to be shown on login screens, emails, etc.
WildFly 10.0.0.CR5 – Keycloak is now built on top of WildFly 10.0.0.CR5. Deploying the server overlay to WildFly 9 is no longer supported

完整内容请看： JIRA

Keycloak 是一个为浏览器和 RESTful Web 服务提供 SSO 的集成。基于 OAuth 2.0 和 JSON Web Token(JWT) 规范。最开始是面向 JBoss 和 Wildfly 通讯，但已经计划为其他诸如 Tomcat、Jetty、Node.js、Rails、Grails 等环境提供解决方案。