Testing bottleneck

Good evening,

We use auth0 as the authentication and it works really good.

However, we have a significant number of e2e and api integration tests.

For all the tests it has to make a call to your servers to get a jwt token.

Unfortunately that process is adding seconds to each test and causing significant delays to our dev / test and ci/cd pipeline.

There has to be a way to avoid constantly hitting your servers (we’ve had to throttle our test framework so we don’t look like we ddos you)

My question is how can I achieve that win-win situation? Can I generate a token locally myself and avoid calling you? Do I try and do some caching?

What is the recommended way to mock that call and pass generic working token to all my apis?

Vinny

Hey there!

Sorry for such delay in response! We’re doing our best in providing the best developer support experience out there, but sometimes the number of incoming questions is just too big for our bandwidth. Sorry for such inconvenience!

Do you still require further assistance from us?