Getting 403 forbidden error: access denied for client Ip

Hi Team,

There was a recent migration of proxy from edge to hybrid. The proxy works fine in edge. But when I test the same flow in hybrid I see 403 forbidden error. 

There is an access control policy which allows set of IPs. But since we are testing through postman, we can't set a specific IP to allow. 

Not sure where it is breaking. Please suggest. Let me know if any other info is required.

0 2 634
2 REPLIES 2

Your policy should contain the configured list of allowed or blocked IP addresses unless these are dynamically set via variables for example in which case you may need to find the source. 

You can also use the debug tool to see details of the incoming request to compare with the configured policy.

Yes, there are list of proxies which are  allowed. But request through postman So here source is Postman, which generates different IPs everytime I send request. So we can't add that,  since dynamic IPs.

In debug it shows "access denied for client Ip -----" at the first step of the flow.

IMG_20230705_171720.jpg