Describe the bug
I'm new to keycloak and keycloak-benchmark.
Some things I noticed that you may want to fix
- The manual configuration steps listed on https://www.keycloak.org/keycloak-benchmark/benchmark-guide/latest/preparing-keycloak are hard to follow. I guess they might have been written with an older version in mind.
- Setting up things with
initialize-benchmark-entities.sh and then running kcb.sh resulted in status.find.is(200), but actually found 404 errors. Setting the realm name like ./kcb.sh --realm-name=test-realm fixed this issue.
- I'm using k8s and having to download a keycloak distribution to get
kcadm.sh felt a bit weird. Maybe running benchmarks from a container that has everything bundled together would be nice?
Version
26.3.5
Expected behavior
No response
Actual behavior
No response
How to Reproduce?
No response
Anything else?
No response
Describe the bug
I'm new to keycloak and keycloak-benchmark.
Some things I noticed that you may want to fix
initialize-benchmark-entities.shand then runningkcb.shresulted instatus.find.is(200), but actually found 404errors. Setting the realm name like./kcb.sh --realm-name=test-realmfixed this issue.kcadm.shfelt a bit weird. Maybe running benchmarks from a container that has everything bundled together would be nice?Version
26.3.5
Expected behavior
No response
Actual behavior
No response
How to Reproduce?
No response
Anything else?
No response