Skip to content
This repository has been archived by the owner on Jul 15, 2021. It is now read-only.

Rate Limiting per Group #24

Open
BK01 opened this issue Jul 6, 2017 · 4 comments
Open

Rate Limiting per Group #24

BK01 opened this issue Jul 6, 2017 · 4 comments
Assignees

Comments

@BK01
Copy link
Contributor

BK01 commented Jul 6, 2017

Is your feature request related to a problem? Please describe.

Rate limits are applied to endpoints, or at anonymous calls vs. API key holders.

Describe the solution you'd like

Implement functionality to allow API owner to set a separate (or the same) rate limit per group. This will allow for a more detailed approach to rate limiting based on individual groups.

@pauldaustin
Copy link

Kong doesn't support plugins (e.g. rate-limiting) by group. Only by consumer or for a whole API.

In fact kong doesn't even have a concept of a group. It has acls, which are like groups, but it's not a concrete concept. An acl for a API is just a list of group names. And for a user they have a list of group names they are a member of. But there isn't a group object that things could be tied to.

This functionality would likely require deep architectural changes within kong for it to work, or a new plugin that has it's own data.

I'd like to hold off on this to version 1.2.0 once we get the existing 1.1.0 functionality finished.

@BK01
Copy link
Contributor Author

BK01 commented Jul 7, 2017

Issue on hold. To be re-evaluated after 1.1.0.

@pauldaustin
Copy link

Let's see if kong will support this:

https://discuss.konghq.com/t/support-for-attaching-api-plugins-to-groups/482

@BK01 BK01 changed the title Rate limiting per group Rate Limiting per Group Nov 28, 2018
@wjykl33
Copy link

wjykl33 commented Feb 25, 2020

Let's see if kong will support this:

https://discuss.konghq.com/t/support-for-attaching-api-plugins-to-groups/482

Hello,Excuse me, whether this function has been implemented?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants