Answer by prabhat · Jan 13, 2016 at 07:34 PM
Currently, edgemicro only honors the proxy name. More details:
1. You create edgemicro_ prefixed proxy with base path and target.
2. You add this proxy to a product let's call it edgemicro-prod1
3. When API call is made through edgemicro using apiKey or JWT token, edgemicro checks if basepath of API matches with basepath of edgemicro_proxy that is approved for list of products approved for that key.
We can add more rules if needed but we did not want to complicate things unless we have to. Hope it helps.
Answer by mikael.mellgren · Jan 15, 2016 at 07:36 AM
I have 2 identical products with 2 different dev-applications associated (2 api-keys) One has /** as resources. The other does not, only the target endpoint.)
Using curl and api-keys. The api-key associated with the first product (with /** in resources) always works The api-key associated with the second product (without /** only with the target endpoint in resources) Fails with access_denied
what about re-using key/secret combinations between instances of microgateway? 1 Answer
Is there any trial(free) Edge Micro available? 1 Answer
How often - and under what circumstances - does the Microgateway "pull" from Edge? 1 Answer
How to access App custom attributes within Microgateway? 3 Answers
Strategies for restarting lots of Edgemicro clients when Edge Cloud configuration changes 1 Answer