Thanks for your reply!
I forgot to copy the relevant parts of our Yaml file (AFAIK using Yaml over
properties should not change behavior of Spring Boot) to the demo project,
but after doing so the same stacktrace still occurs. I've pushed an update
to the repository with the correct Yaml file.
The stacktrace seems very related to the usage of Jetty, so I think that's
part of the problem. Other than that, my repository is quite similar to
your demo so I don't see what could otherwise be causing this behavior...
On Fri, Oct 7, 2016 at 5:14 PM Niko Köbler <niko(a)n-k.de> wrote:
I just had a quick look into your GitHub repo and didn’t run any boot app
with Jetty so far, but what I figured out is, that your
application.properties file is completely empty. That’s normally the place
where to put your Keycloak properties. Without them, the KC adapter doesn’t
know what to do… Have a look at my KC Spring Boot Example:
perhaps this will help
you (and of course, have a look into the official KC documentation!)
Am 07.10.2016 um 12:57 schrieb Bas Dalenoord <bdalenoord(a)gmail.com>:
I'm trying to secure a Spring Boot-based application using Keycloak, but as
soon as I include the 'keycloak-spring-boot-adapter' artifact, my
application does not start anymore, throwing seemingly unrelated
exceptions. I'm following this tutorial
the backend part, but I upgraded all version numbers to the latest final
I've created a stripped down version of the application with which I can
reproduce the errors. It can be found on my GitHub
;. If I remove the
adapter-artifact, everything starts normally. I'm guessing it has to do
with Spring Boots autoconfiguration, but I cannot figure out what I should
change to get everything working.
Can anyone tell me what I'm doing wrong and what I can do to fix the
keycloak-user mailing list