Skip to content
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

Receiving 'found nothing' error when using LoginUserPassword or AuthorizationCode scenarios. #1049

Open
mahakrishnan-cb opened this issue Nov 21, 2024 · 1 comment
Assignees

Comments

@mahakrishnan-cb
Copy link

Describe the bug

I have a Keycloak instance running in an EKS cluster with 2 replicas. I want to perform performance testing on user logins, so I used Keycloak's benchmark-module to conduct the tests. Below is the command I executed:

./bin/kcb.sh \
--scenario=keycloak.scenario.authentication.LoginUserPassword \
--server-url=<server-url> \
--realm-name=master \
--client-id=<client-id> \
--username=<user-name> \
--user-password=<user-password> \
--users-per-sec=1 \
--concurrent-users=5 \
--measurement=600 \
--log-http-on-failure

Upon execution, I encountered the following error:

13:27:30.283 [DEBUG] i.g.h.e.r.DefaultStatsProcessor - Request 'Browser to Log In Endpoint' failed for user 2: regex(action="([^"]*)").find.transform.exists, found nothing

I tried adjusting various configurations, but none resolved the issue; they all led to the same error. However, other scenarios like keycloak.scenario.authentication.ClientSecret and keycloak.scenario.admin.ListSessions work fine for me.

Since I faced this issue with Keycloak v23.0.6, I upgraded my Keycloak instance to v25.0.5 and used Keycloak Benchmark 0.13. Unfortunately, I still encounter the same error.

Version details:

Keycloak Benchmark Module: Keycloak Benchmark 0.13
Keycloak Version: 25.0.5

Version

25.0.5

Expected behavior

No response

Actual behavior

No response

How to Reproduce?

No response

Anything else?

No response

@ahus1 ahus1 self-assigned this Dec 13, 2024
@ahus1
Copy link
Contributor

ahus1 commented Dec 13, 2024

Thank you for reaching out. To debug your issue, please log all HTTP requests by changing the --log-http-on-failure to --log-http-always.

When looking at the login page in the debug output or at the Keycloak instance (possibly when running with debug enabled), you should see an error message. for example that the client used for the login is not known.

When looking at the regex that fails here, you'll see that it looks for an action in the web page returned, and I suspect it is missing due to the error.

Let me know if this helps your situation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants