Support setting quota and rate limits against oauth2 client id

[amadeus-x1]

Do you want to request a feature or report a bug? feature

What is the current behavior? When creating access tokens against oauth2 client id, quota and rate limits apply separately to individual access tokens.

What is the expected behavior? Have an option to support quotas and rate limits and client id level.

[letzya]

Really good feature. A developer can have a client_id can have a few "live" access_tokens since he is writing an app that is being tested in a few environments but essentially they are all the same client_id from the api owner perspective. The api owner doesn't care how many live tokens are out there as long as they are all using the client_id's quota.

[letzya]

Required by another user

[christtyk]

Would like this to stay open - request from multiple users

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs, please add comments to this ticket if you would like it to stay open. Thank you for your contributions.

[christtyk]

bump

[andyo-tyk]

This is logged on our product roadmap and we will ensure this is considered when we next look at this part of the code; I am closing the request here due to the age.

I will update this ticket as and when we implement something.

Thank you for supporting Tyk.