Closed pdavie closed 1 year ago
Which operating system are you using and what's your Docker + Docker Compose version?
The highlighted WARN
seems less critical and I'm wondering why Keycloak stops because of an invalid login attempt.
I assume, every web test (*WT
) is therefore currently failing on your side?
I am using Windows 10 Pro with Docker Desktop. With Docker on Windows, there are two options to run containers, Windows Containers and Windows Subsystem for Linux. Unfortunately, I have had no success with either.
Yes, unfortunately, the testing container stops because Keycloak exits which means that all of the web tests cannot run. The really odd thing is that I can run the Keycloak docker image separately without any difficulty. I guess I could try taking Keycloak out of the docker-compose.yml file and start a separate container for Keycloak and see if this makes any difference... I will try to remember to do this and get back to you with the outcome.
@pdavie can you try to run all tests with mvn verify
and the recent code? I did add some improvements for Windows and tried it on my Windows machine (aka. it works on my machine).
I have just updated the code and run mvn verify and am still having issues with docker. I will try it again when I have some spare time. Thank you for your help.
Going to close this due to inactivity, please feel free to ping me if the issue persists @pdavie
I am having an issue with Keycloak when starting the web test profile. This is the error log from the Keycloak docker container, there is an apparent problematic line which I have highlighted below (in context):
00:08:39,160 WARN [org.keycloak.events] (default task-4) type=LOGIN_ERROR, realmId=spring, clientId=null, userId=null, ipAddress=172.18.0.1, error=expired_code, restart_after_timeout=true, authSessionParentId=b07fcde2-41a2-4102-a778-24d51d6a44e1, authSessionTabId=iPqoHSnkW1U
Any thoughts?