Open apps4ulok opened 9 years ago
Is that the actual URL you're using? It should include the name of your organization before the dash:
http://{ORGANIZATION}-test.apigee.net/apigee-remote-proxy/apigee-remote-proxy/verifyAPIKey
it was a typo. i am using org name. as per apigee-127 docs, creating remote service creates a remote service, developer application, developer and a product. and also, it assigns remote proxy under product. once remote proxy developer application is assigned under a product, it will have a api key which can be used to 'x-DNA-Api-Key' as header param. and body contains a actual developer API key which needs to be validated. But 'apigee-remote-proxy' creates only remote proxy. it is not associated with any product. if so, how do i get a api key which i can pass for header param: x-DNA-Api-Key?
If you aren't using apigee-127, you'll need to do this yourself. You must associate the proxy with a product. That is the only place you'll be able to get a valid client key.
thank you for the response. i noticed that it always creates proxy with name 'apigee-remote-proxy'. is there way to supply name of the proxy as an input?
Not at present. However, you could certainly rename it on Edge.
Hi I followed steps and created remote proxy. i can apigee-remote-proxy in the apigee edge. how can i validate api key using this remove proxy? when i hit http://-test.apigee.net/apigee-remote-proxy, it is asking for an api key.
i have created couple of developers and developer apps. when i give the api key of that developer app int he header: x-DNA-Api-Key, it gives me an error message: Invalid ApiKey for given resource
URL i tried to validate developer key as: http://-test.apigee.net/apigee-remote-proxy/apigee-remote-proxy/verifyAPIKey
Body: {"apiKey": "developer key"}