Wildcard support in proxy basepath with edgemicro

[#1]

We wish to take advantage of the wildcard feature in proxy basepath with edgemicro.

For example we require separate proxies (linked to separate products) for api patterns like

account/<accountNum>/resourceA/...

account/<accountNum>/resourceB/...

With edge (cloud) Separate proxies are possible using the wildcard within base paths. e.g.

account/*/resourceA

account/*/resourceB

and then some magic to extract the variables and rewrite the target path to include the accountNum/resource

This seems a common pattern, however since edgemicro does not have support for policies/scripting.

QUESTION: Is this at all possible with edgemicro

QUESTION: What would be the best approach to extend/enable this functionality

Ideally the */resource is automatically appended to the target url.

[#2]

This issue is a challenge for us as we need our API Proxy definitions to be differentiated for each of those cases for our OAuth Scopes to work correctly.

[Former Community Member]

This feature is currently not supported by EdgeMicro. If you'd like to open an issue, we can look to add it in the future releases.

[#4]

you guys have me all curious as to WHY you need to do this now.. its kind of driving me crazy 🙂

[#5]

HI @Benjamin Goldman

We have our existing APIs in this format. To give a more specific example -

/user/<user_id>/profile

/user/<user_id>/shoppinglist

Above are different APIs, with there crud operations. They are separate functionally and also we want to restrict access to one or more of these APIs using products.

Thanks,

Jaskaran