Portal-Published API changes Not Reflecting in Layer7 Gateway

[Sunil Kumar]

Hi Team,

We are encountering an unusual issue with a portal-published API. Here's the setup &  scenario:-

API Gateway – 11.1.1

Developers Portal -5.2.3 or 5.3

• A portal user with Org Publisher access is created in the portal, enabling them to create, update, and delete APIs published within the same organization.
• The user can successfully create and delete APIs, in that Organization but when they attempt to modify the API (e.g., updating routing, adding out-of-the-box or custom policy templates available on the portal), the changes are saved in the portal but are not reflected in the Layer7 Gateway, when you check the changes from  policy manager. Refer below screen shots.
• Policy on Portal
• 
• Policy on gateway - As you can see the routing has been updated to /test2 on the Portal side but the Policy on the gateway still shows /test1
• 

It appears that somehow the changes made in the portal are not being sent to the Gateway. This behavior has been observed in both Portal versions 5.2.3 and 5.3.

According to the Broadcom Tech Docs, users with Org Publisher access should be able to modify API policies (under Manage Permissions), but this functionality seems to be inconsistent or not working as documented or I am missing something.

https://techdocs.broadcom.com/us/en/ca-enterprise-software/layer7-api-management/api-developer-portal/5-0/user-types-roles-and-permissions.html

Additionally, when you login as an admin user to the Developer portal and make the same changes this gets updated on the Portal as well as the Policy on the Gateway ,without any issues.

Has anyone else experienced this issue or have suggestions on resolving it? Any insights or guidance would be greatly appreciated.

Thanks in advance for your help!

[michal hulman]

Hello,

I had exactly this issue too (with API GW 10.1) and I solved it by going to Edit Proxy

and there under Organization Assignement select Organization where the user with Org Publisher permissions belong:

Then Save it and try again.

Please let me know if it also helped you. Thanks

[Sunil Kumar]

Hi Michal,

Thanks for the quick update. Much appreciated. I did a quick test. looks like its working. Checking more on this.

Couple of questions though :-

1. How come add & delete api options were working for the same user without this selection in the proxy? I didn't had any Org selected in the proxy

2. We already have our Gateway 11.1.1 enrolled with Portal 5.2.3/5.3.Does editing the proxy and adding Orgs for Organization assignment will have any other impactions or impacts?

3.Is there any guidance/KB from Broadcom on Organization Assignment for the Proxy? Apparently the below tech doc does not talk much about this in step#9

https://techdocs.broadcom.com/us/en/ca-enterprise-software/layer7-api-management/api-developer-portal/5-3/install-configure-and-upgrade/post-installation-tasks/enroll-a-layer7-api-gateway.html

 

Thanks

Sunil