Receiving a 403 Forbidden API Error Message

We are running performance testing in our Brightspace test server with 7% failures related to "403 Forbidden" error messages.

Perf Testing: We are automating 18 users to load the widget every second for 1 minute—equaling to about 1,080 users in a minute.

Background: We have 4 back-end servers with round-robin traffic running a custom widget within our Brightspace test domain. Each server is equipped with its own refresh token and the ability to generate new ones.

Our performance testing is to check how many concurrent users logged in can load the widget at the same time. Since our student base reaches around ~350,000, we can estimate around 1000 users concurrently using the widget at any given minute (max possible users).

Even though the widget continues to work, the 403 Forbidden error messages continue to appear in every perf test.

Could this be the cause of insufficient server resources or are we capping the rate limit of our API endpoints?

Tagged: