If i compare the auth url from my local environment and the url from production the fact is that the “code_challenge” and “code_challenge_method” query params are missing.
Hi!
I faced with the same behavior, and when I rollback to 8.0.2 version - error was the same.
But I have only test stand and clean all was an option.
So I resolved it by full cleaning of docker containers and data (i’m not good deal with docker and for me it taked two attempts).
I can add that this problem not only with admin console, but with every login too.
And after cleaning all I restored version 8.0.2 and it worked fine. And after pulling 9.0.0 version all worked fine again. So it looks like the cause is in some settings that was done while using keycloak 8.0.2.
in my case clearing browser cache / incognito browser window did not work.
i assume either something during migration went wrong or a specific combination of my configuration caused problem on the new version.
either way, my fix was to remove a line from database.
table: client_attributes
row with:
value S256
name: pkce.code.challenge.method
after removing this line i was able to login again without any problem.
i am yet to know the implications of removing this configuration…
Can you take a look at app.js to check if it’s including (look at index.html for the admin console to find the URL of it. It’ll be something like /auth/resources/lnz3u/admin/keycloak/js/app.js):
Seems somehow you are getting an old version of app.js loaded, which shouldn’t be possible. Unless you have an old and a new version of Keycloak running at the same time, or have some caching layer on top or something.
BTW browser cache shouldn’t have anything to do with this issue. The index.html page of the admin console is not cached, and all resources it uses includes a string that is updated on a release.
INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: Keycloak 9.0.0 (WildFly Core 10.0.3.Final) started in 24932ms - Started 684 of 989 services (701 services are lazy, passive or on-demand)
I found a solutions for this it is related to either a file in your
standalone
themes
folder.
So i guess it is an old admin theme like @stianst already said.
I got my self a fresh copy of KC and unzipped the standalone and theme folder.
This solved it on my end. @tiago.diogo
Copying the /theme folder solved it for me too. But the structure of the theme must have changed because everything is broken. Do we need to do the theming from scratch for every new version?
Instead of messing with the theme files, I found out that removing the volume and recreating it solved the problem too. No changes to the theme files were needed this way.