Keycloak 1.2.0.CR1 發布，SSO 集成解決方案
Keycloak 1.2.0.CR1 發布，更新了管理控制臺、 登錄頁和帳戶管理，以更好地適應 PatternFly 的外觀和感覺。使得 Keycloak 和其他 JBoss 項目之間能夠更好地集成。在客戶端方面，將 Keycloak 應用程序和 oauth 客戶端合并成一個客戶端了，管理更加輕松了。
此外，還有一些新增功能：
-
Token mapping - Through token mapping it's possible to pull in additional information from brokered identity providers
</li> -
Store and retrieve external token - It's now possible to store the token retrieved from brokered identity providers. Clients can retrieve this if they need to invoke services secured by the external identity provider.
</li> -
Persist and manage consents - When a user consents access to a client the consents are now saved. Users can also view and manage consents given to clients through the account management console.
</li> -
Password Policies - Through password policies it's now possible to prevent re-use of previous passwords, require users to regularly update their password and also provide a regular expression for required password format.
</li> -
HttpClient SPI - The introduction of a HttpClient SPI makes it possible to configure the HTTP connections initiated by Keycloak. For example to provide a trust store.
</li> -
KeycloakContext - KeycloakContext is exposed through KeycloakSession and gives providers access to HTTP headers, cookies, query parameters, etc.
</li> -
Logging Updates - The JBoss Logging event listener is now enabled by default for new realms. This makes it easier to view debug log information for login events.
</li> -
Spring Security Adapter preview - We now have a Spring Security Adapter. There's is no documentation and we haven't tested it thoroughly so consider this a preview.
</li> </ul>更多內容請查看發行頁面。
Keycloak 是一個為瀏覽器和 RESTful Web 服務提供 SSO 的集成。基于 OAuth 2.0 和 JSON Web Token(JWT) 規范。最開始是面向 JBoss 和 Wildfly 通訊，但已經計劃為其他諸如 Tomcat、Jetty、Node.js、Rails、Grails 等環境提供解決方案。來自：http://www.oschina.net/news/62153/keycloak-1-2-0-cr1
本文由用戶 bgn4 自行上傳分享，僅供網友學習交流。所有權歸原作者，若您的權利被侵害，請聯系管理員。轉載本站原創文章，請注明出處，并保留原始鏈接、圖片水印。本站是一個以用戶分享為主的開源技術平臺，歡迎各類分享！