-
Notifications
You must be signed in to change notification settings - Fork 315
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Local development environment fails to start #424
Comments
In addition to the provided fix, I could also upgrade the local Keycloak version to 11.0.2. This requires to add an additional method I'll send a separate PR for this once this gets merged. |
Hey @thomasdarimont, thanks for issue. The information you're providing here is very helpful. For some context, I originally wrote the example custom user federation provider back when I was running Keycloak 4.8.3.Final in order to test the Anyways, I did a fresh clone of this repository and followed the steps you outlined and I wasn't able to reproduce the NPE that you seem to be running in to. For me, Keycloak started just fine, and I was able to use the I also tested the contents of #425 locally, and everything seems to be working just fine with the changes you suggested as well. So I'm perfectly happy to defer to your Keycloak expertise and accept those changes. Although I am curious if you have any thoughts about why the code that's currently in Thanks! |
Keycloak fails to start when running the local Keycloak development environment for the terraform-provider-keycloak,
due to a
NullPointerException
.Steps to reproduce:
Run in terminal 1
make user-federation-example
make local
Run in terminal 2
docker-compose logs -f
Output:
Currently Keycloak is configured with this volume mapping to expose the custom-user-federation for testing:
With remote debugging I found out, that the NPE is triggered because dir.listFiles(...) returns null here:
https://github.com/keycloak/keycloak/blob/master/services/src/main/java/org/keycloak/provider/FileSystemProviderLoaderFactory.java#L53
Also
/opt/jboss/keycloak/providers/
is not supported by Keycloak since many moons.A better way would be to expose the extension via the supported
/opt/jboss/keycloak/standalone/deployments
folder:once this is fixed, the example still fails, because of classloading issues:
The extension jar is missing a
META-INF/jboss-deployment-structure.xml
file which makes the required Keycloak modules available to the extension classpath.The text was updated successfully, but these errors were encountered: