Replies: 1 comment
-
|
You can see my workaround for the custom provider deployed in Keycloak 18 Quarkus. #11973 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I have custom provider for LoginForms, with name "myloginform". It's running in previous keycloak versions (16) but when I'm triying to migrate to the new version (18) I can't deploy it correctly.
I moved my jar to providers dir and I executed:
bin/kc.sh build --spi-login-forms-freemaker-enabled=false --spi-login-forms-myloginform-enabled=true --spi-login-forms-provider=myloginform
When I run with "start-dev", I can see how the "build" is executed another time (shows info for the jar detected) but when I'm trying to access, I get a NullPointerException because de LoginFormsProvider is null.
How I must deploy the jar? I follwed the doc steps with no luck.
Beta Was this translation helpful? Give feedback.
All reactions