Is it possible to configure higher throughput for the OAuth 2.0 token refresh endpoint? Running JMeter scripts with 50 concurrent threads on Genesys Cloud US1. The goal is testing peak login capacity for agent workforce. Current setup uses standard SAML 2.0 IdP.
When threads hit 45, the /oauth/token endpoint starts returning 429 Too Many Requests. This blocks the entire flow because agents cannot authenticate to the WFM module. The error response includes Retry-After: 5.
The environment is Genesys Cloud US1. Using JMeter 5.6.2. The load pattern is a ramp-up over 10 seconds to simulate morning shift login surge.
This rate limit seems too strict for a load testing scenario. We need to validate if the authentication service can handle 100 logins per second. The standard documentation does not mention specific limits for token refresh during high concurrency.
We are blocked on capacity planning. Can an admin increase the quota for this endpoint? Or is there a specific header to include in the JMeter request to avoid throttling? The current configuration uses basic auth for client credentials grant. Any guidance on adjusting this for load tests would be helpful.