API ID value Changing when "Set AS Portal Managed Service" Assertion is Moved

Products

• CA API Gateway

Issue/Introduction

Issue whereby the API ID value in the "Set as Portal Managed Service" assertion changes whenever the assertion is moved during policy development/modification. 

For example, if  move/drag the assertion from line 3 to line 5, the API ID value inside the assertion changes. This causes the API key validation to fail as the value no longer matches the API ID value associated with the API in the Developer portal.

We are aware that importing a new assertion changes the value, but simply moving the existing assertion while modifying a policy should allow the same value to persist, and this has not been an issue in the past.

Environment

Portal 5.x

 

Cause

This is a side effect when fixed the defect regarding the duplicate API ID issue when copying the policy assertion that contains Set as portal Managed service (DE465764).

Resolution

1.  Behavior it has been there since portal 4.5.4
2.  This is a side effect when fixed the defect regarding the duplicate API ID issue when copying the policy assertion that contains Set as portal Managed service (DE465764).
3.  The current behavior is by design on "Set as Portal Managed,  we decided not to fix the defect "Set as Portal Managed  , every move with assertion in workflow changes API ID" (DE496498)