You also need to enable adapter subsystem in standalone.xml :
<extension module="org.keycloak.keycloak-adapter-subsystem"/
Take a look at docs (especially adapter part) for more details.
Marek
On 22/11/15 18:53, Rens Verhage wrote:
Hi all,
I’m having some trouble securing a test application with Keycloak. I downloaded the
keycloak-1.6.1.Final.zip. First thing I did was changing the datasource to PostgreSQL and
in Keycloak configured my realm and generated a keycloak.json file.
I copied keycloak.json to the WEB-INF folder of my war project and edited my web.xml, I
added this:
<login-config>
<auth-method>KEYCLOAK</auth-method>
<realm-name>PDC</realm-name>
</login-config>
<security-role>
<role-name>admin</role-name>
</security-role>
<security-role>
<role-name>user</role-name>
</security-role>
Upon boot however, Wildfly logs the following error:
"WFLYCTL0080: Failed services" =>
{"jboss.undertow.deployment.default-server.default-host./pdc-web" =>
"org.jboss.msc.service.StartException in service
jboss.undertow.deployment.default-server.default-host./pdc-web:
java.lang.RuntimeException: java.lang.RuntimeException: UT010039: Unknown authentication
mechanism KEYCLOAK
Caused by: java.lang.RuntimeException: java.lang.RuntimeException: UT010039: Unknown
authentication mechanism KEYCLOAK
Caused by: java.lang.RuntimeException: UT010039: Unknown authentication mechanism
KEYCLOAK”}}
The only hint to fix this error that I could find was to make sure that the Keycloak
subsystem is enabled in standalone/configuration/standalone.xml, which is the case as I
didn’t change the default config:
<server xmlns="urn:jboss:domain:3.0">
<extensions>
...
<extension module="org.keycloak.keycloak-server-subsystem"/>
...
</extensions>
…
</server>
As my experience with Wildfly and knowledge of Keycloak is limited, what could be the
problem here?
Regards,
Rens Verhage
_______________________________________________
keycloak-user mailing list
keycloak-user(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-user