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
To explore and decide on the implementation of data access limits for users accessing both restricted and open resources. The goal is to establish constraints on API calls, data size, and overall usage to ensure fair and controlled access.
Key Topics for Discussion
Daily and Monthly Access Limits:
Question: Should we implement daily and monthly limits on API calls and data usage?
Do we need to restrict the based on the size of data accessed via API calls?
Current Policy on Restricted vs. Open Resources:
Issue: Currently, limits are set only for restricted resources, with no limits on open resources.
Proposal: Establish default access limits for open resources if no explicit policy is created.
Question: Is it possible to create a policy for resources without specifying the consumer? This would apply to open resources
and ensure consistent access control.
Application-Level User Restrictions:
Question: How can we implement user-level restrictions at the application level?
Examples:
-> Limit the number of API requests a user can make regardless of the specific resource.
-> Apply access limits to various API endpoints, such as list APIs and others in the application (e.g., cat-server).
The text was updated successfully, but these errors were encountered:
To explore and decide on the implementation of data access limits for users accessing both restricted and open resources. The goal is to establish constraints on API calls, data size, and overall usage to ensure fair and controlled access.
Daily and Monthly Access Limits:
Question: Should we implement daily and monthly limits on API calls and data usage?
Do we need to restrict the based on the size of data accessed via API calls?
Current Policy on Restricted vs. Open Resources:
Application-Level User Restrictions:
The text was updated successfully, but these errors were encountered: