Hawtio is already supporting Keycloak as OpenID Provider. However, Keycloak already announced that the configuration methods used by Hawtio are deprecated.
+Hawtio is already supporting Keycloak as OpenID Provider. However, Keycloak already announced that the configuration methods used by Hawtio are deprecated.
Because OpenID Connect Core 1.0 is a widespread specification and standard method for distributed authentication (based on OAuth 2), Hawtio 4 now supports generic OpenID authentication.
@@ -262,7 +262,7 @@These libraries are included in Hawtio Server WAR, which means there’s no need to install/deploy any additional libraries (as it is the case with Keycloak specific configuration).
+These libraries are included in Hawtio Server WAR, which means there’s no need to install/deploy any additional libraries (as it is the case with Keycloak specific configuration).
In order to configure Hawtio with external OpenID Connect provider, we need to provide one configuration file and point Hawtio to its location.
@@ -293,7 +293,7 @@Unlike with Keycloak specific configuration, there’s only one *.properties file needed that is used to configure all the aspects of OpenID Connect configuration. Here’s the template:
Unlike with Keycloak specific configuration, there’s only one *.properties file needed that is used to configure all the aspects of OpenID Connect configuration. Here’s the template: