This website uses Cookies. Click Accept to agree to our website's cookie use as described in our Privacy Policy. Click Preferences to customize your cookie settings.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
- About pengdu30
pengdu30
New Member
Since
10-15-2018
06-22-2021
My Stats
- 26 Posts
- 0 Solutions
- 0 Likes given
- 0 Likes received
thardy's Bio
Badges pengdu30 Earned
View all badgesRecent Activity
06-24-2019
When we test Microgateway running on our On-Prem Linux VM, we noticed
the download time showing on Postman response panel is always over
200ms. We tested simple NodeJS running on the same Linux VM which does
not have the same issue. We also tested ac...
Since v2.4.12 the cache policy enabled to improve the apikey verify
performance, which exact parameter in this proxy on Apigee Edge config
how long the value will be cached on Apigee Edge by the cache policy.
Thanks.
Trying to do a test using basic auth to access Apigee Edge API Proxy and
found after successfully verify api key the variable
verifyapikey.VerifyAPIKey.client_secret value is blank. Here is the
policy I'm using in PreFlow: verify-api-key
According t...
Based on the Apigee Document Using wildcards in Microgateway-aware
proxies the feature supported in v2.4.x, I could not find any apiproxy
example to see how this works, especially not clear how should target
URL to be configured when wildcard present...
For edgemicro aware apiproxy is XML declaration standalone="yes" has any
impact to how apiproxy behaves?The reason why I'm asking is when testing
using apigee-deploy-maven-plugin to deploy edgemicro aware apiproxy I
found out in the generated xml fil...
In Create OAuth Request policy there's one token_expiry config:
token_expiry 300
Is this the parameter control how long the JWT for Edge
Microgateway apikey verify request cached on Apigee Edge? If it is,
please also confirm the unit of the cache ti...
04-26-2019
Found the issue, in Condition the variable name need to be surrounded by
{...}, found this when reading
https://community.apigee.com/questions/34852/apikey-from-oauth-for-use-in-separate-proxy-with-s.html
{verifyapikey.VerifyAPIKey.client_secret} !=...
04-26-2019
Have some additional findings, if I remove the Condition step, actual in
the next step I can see the flow variables populated correctly. Now the
issue looks like related to the way how to add the Condition step,
should this be wrapped in a policy in ...
04-26-2019
After verify-api-key step, I have following step, which catched the
mismatch: verifyapikey.VerifyAPIKey.client_secret !=
request.queryparam.password
RaiseFault-SecretMismatch