"/" mandatory as a resouce path if api-key authentication is required

[#1]

Hi,

I've created a proxy with a127 and added api-key security as described in https://github.com/apigee-127/a127-documentation/w... When I deploy this proxy on my edge-server and create a product including this proxy, registered developer apps get the following message when they try to call the proxy:

"com.apigee.rest.framework.ResourceNotFoundException{ code = keymanagement.service.apiresource_doesnot_exist, message = APIResource / does not exist, associated contexts = []}"

I can solve this issue by adding "/" as a Resource Path to the product. Is this the way to go or does it expose any security issues? A products with "/" as a Resource-Path and without any proxies attached to it allowes its users to call any proxy deployed on the edge server.

When I add a proxy, the clients are restricted to use only the proxies definined within the product. This is the desired behaviour.

Regards,

Frederik