-
Bug
-
Resolution: Done
-
Blocker
-
None
-
None
We have the following wildfly-s2i example that demonstrates how to set up the automatic SAML client registration on OpenShift:
https://github.com/wildfly/wildfly-s2i/pull/422
Some dependency versions need to be updated as mentioned on the PR.
However, even after updating these, I seem to be running into the following exception in the server log for my saml-app on OpenShift:
19:30:03,413 WARN [org.keycloak.adapters.saml.elytron.KeycloakConfigurationServletListener] (ServerService Thread Pool -- 62) No adapter configuration. Keycloak is unconfigured and will deny all requests. 19:30:03,421 WARN [io.undertow.servlet] (ServerService Thread Pool -- 62) UT015020: Path /secured is secured for some HTTP methods, however it is not secured for [TRACE, HEAD, DELETE, POST, CONNECT, OPTIONS, PUT] 19:30:03,425 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 62) MSC000001: Failed to start service jboss.deployment.unit."saml-app.war".undertow-deployment: org.jboss.msc.service.StartException in service jboss.deployment.unit."saml-app.war".undertow-deployment: java.lang.RuntimeException: java.lang.IllegalStateException: The required mechanism 'KEYCLOAK-SAML' is not available in mechanisms [BASIC, CLIENT_CERT, DIGEST, FORM] from the HttpAuthenticationFactory. at org.wildfly.extension.undertow@29.0.0.Final//org.wildfly.extension.undertow.deployment.UndertowDeploymentService$1.run(UndertowDeploymentService.java:90)
When looking at the server configuration, the keycloak-saml subsystem has been added successfully by the keycloak-saml-adapter-galleon-pack but is empty.
It seems like the wildfly-cloud-galleon-pack's keycloak launch script isn't getting executed at all for some reason. The SAML client also isn't getting added on the Keycloak side.
- is related to
-
-
- Closed
-
- relates to
-
-
- Closed
-
