You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If a user creates a huge number of API keys the route to list their API keys could become to expensive. In the future we could paginate that route, but for now I propose to put a reasonable limit on the number of active API keys per user. Also, we should verify that the route does not include deleted/inactive keys.
When a user hits the limit, the remedy is to delete disused keys.
The text was updated successfully, but these errors were encountered:
If a user creates a huge number of API keys the route to list their API keys could become to expensive. In the future we could paginate that route, but for now I propose to put a reasonable limit on the number of active API keys per user. Also, we should verify that the route does not include deleted/inactive keys.
When a user hits the limit, the remedy is to delete disused keys.
The text was updated successfully, but these errors were encountered: