Connection Pool and OAuth2 logins

I have some trouble with failing OAuth2 logins.

I have much less test accounts on the system under test than VUs. The login fails when the same account tries to login multiple times in the same time frame.

I assume that the problem is related to the connection pool. I set noConnectionReuse and noVUConnectionReuse without success.

I cannot add more test accounts. So I wrote an extension for semaphores. But serializing the login per account, limits the amount parallel logins as well.

Are there other ways to disable the connection pool in k6 or go?

Hi @crumble,

Thanks for your question. So the issue you are facing is:

  1. You run a test with many VUs;
  2. You have a small number of test accounts;
  3. If a login is attempted with the same account in a given time frame, then eventually the login will fail.

I have some questions that might help me understand the problem further:

  1. How many VUs are you using in the test?
  2. What is the time frame?
  3. What error do you get back from the auth server when the login fails?
  4. Could it be a rate limit or some sort of policy that is preventing multiple logins to the same account in the given time frame?

Best,
Ankur