Conflicting Behaviour When API-Level and Common Policies Share the Same Name

[JanakaPushpakumara]

Description

When an API-level policy and a common policy share the same name, conflicting behaviours have been observed.

Steps to Reproduce

The following steps were carried out to reproduce the issue:

1. We created an API and assigned an API-level policy named sample-policy:v1.
2. Next, we created a common policy with the same name but with an updated policy file.
   With this setup, we observed the following behaviours:

• In the API-level policy management window, clicking the download option resulted in the updated policy file (the newly created common policy) being downloaded. However, the attached policy remained the one initially assigned at the API level.
• In the API Publisher page, within the API-level policy management window, only the API-level policy is visible in the policy list on the right. The global policy does not appear unless the API-level policy is manually deleted.
• When both the API-level policy and the common policy with the same name exist, clicking the view mediation policy button displays the API-level policy, not the common policy.

Affected Component

APIM

Version

4.2.0

Environment Details (with versions)

No response

Relevant Log Output

No response

Related Issues

No response

Suggested Labels

wso2am-4.2.0