question: Having trouble getting my app to use the customerKey for the product rather than the remote proxy when deployed to Apigee .... about a127-documentation

[WWitman]

Hi Ed,
I'm going to run through the steps to see if I have the same problem (or not).
Will

[emcpadden]

Thanks Will ... I'm wondering if I'm doing something wrong. I know that when I'm working remotely I need to use the remote proxy so I guess it makes sense that I would use that CustomerKey but I just can't see how to tell it to use the product customerKey that the API belongs to when I am running it from Apigee.

If you could show me what I need to do to run both remotely and on Apigee and how to configure so it works for both using the right CustomerKey.

I really appreciate your help with this. THANKS!

[WWitman]

Hi Ed,

I spent some time trying different scenarios with ApiKey. I think this might be related to a problem, not something you're doing wrong.

Q: In your product (the one you created, not the one associated with the RemoteProxy service) -- is there a Resource Path set? Is it set to something other than "/" or "/**" ?

If the answer is yes, try this: In that product, set the Resource Path to : "/". Remove any other paths. Then, save and hit the proxy again.

[emcpadden]

Hi Will,

I just went to the product and made the resource path just "/" and that did the trick!

Thanks so much for your help with this.

...Ed