Disabling A Policy From The Portal Is Not Reflected On Gateway

Products

• CA API Gateway

Issue/Introduction

After disabling a policy directly on the portal and then looking at the same corresponding policy on the gateway we see that it is still enabled on the gateway side.  Why is the policy not disabled on the gateway?

Environment

All supported versions of the CA API Gateway

Resolution

This is expected behavior.  

Disabling a portal published api from the portal side does not disable the corresponding policy on the gateway side.  When disabling a portal published api it has the effect that the API cannot be added to applications. If an API is already added to an application and the state changes from enabled to disabled, the application cannot continue to consume the API.

From the gateway side if you were to right click the portal published api from policy manager->Service Properties->Under additional properties you will see a 'internal.portalAPIEnabled' property.  If the API is disabled from the portal side, then this property will get set to false on the gateway side.  Within the portal service preface policy we check the value of this property and if it is not equal to true then policy execution will fail.