Rate limit assertion issue when we are copying from one Policy to other policy
search cancel

Rate limit assertion issue when we are copying from one Policy to other policy

book

Article ID: 221011

calendar_today

Updated On:

Products

CA API Gateway

Issue/Introduction

When we are creating a policy from an existing policy copy the Rate Limit assertion PRESET showing same and it is sharing the Rate Limit settings and throwing 429 error. 

Also one other policy always giving 429 error. 

 

Environment

Release : 9.4

Component : API GATEWAY

Cause

When you copy the service in policy manager using copy/paste then changing the policy name and url, that includes the RateLimit assertion limit by “gateway node” will maintain the same PRESET count (gateway wide variable) to hold rate limit for each policy.  The result: Limiting access to each policy by the same variable.

 

 

Resolution

Goal is for these policies to limit independently change use custom, define it with a context variable like ${service.name}  this will result in using the service name making each rate limit apply to a single service