Forbidden error while editing product

[amrutachandankh]

Hi All,

I have added a user to a custom role and created a product.The role has get,put,delete permission for that product.The user can delete the product,but he cant edit the product and add api resources like proxies.

Getting "Forbidden!You dont have permission to access the resource" error.

Can anyone please help.

[jaupadhyay]

Hi Amruta

Here is the Apigee documentation page for permissions reference.

https://docs.apigee.com/api-platform/system-administration/permissions#resource-files

Did you create custom role using Edge UI or Management API call? Use Management API call to check the permissions on your custom roles. It should have permissions on following resource path.

/apiproducts

/apiproducts/*

/apiproducts/*/attributes

/apiproducts/*/attributes/*

If you are missing any permission please add those to your custom role. It will let you perform the rquired operation.

[amrutachandankh]

Hi Jayesh,

below are the permissions

"path": "/apiproducts/<productname>", "permissions": [ "delete", "put", "get" ]

"path": "/apiproducts", "permissions": [ "put" ]

"path": "/apiproducts/*", "permissions": []

The user is able to view the product but cant edit it and add proxies into the product

[jaupadhyay]

Hi Amruta

You are using correct permissions.

I have created custom role using above permissions you mentioned and It did work for me.

One more thing to check is ,

When you login on edge UI using user with custom role permission , can you check products page. Under Action column there will be roles button. When you click on that button you should see all three permissions(View Edit Delete) available. If required permission is not available you can amend it from there.

Other thing to check is, does that product have any custom attribute set up already? If you try and save that product you will also require following path with put permission

/apiproducts/*/attributes/*

[amrutachandankh]

Thank you Jayesh.

After giving,get and put permissions to deployments its working fine.

"path": "/deployments", "permissions": [ "put", "get" ]

[jaupadhyay]

@Amruta Chandankhede That's great news and very useful to know how you managed to resolve this issue.