About reinier_vanderh

reinier_vanderh · 01-30-2019

An XMLtoJSON policy with true will round long numbers causing unexpected issues.In our application we use 18-digit codes. We have an XMLtoJSON policy in place which rounds the codes and replaces the last 2 digits with 00:Example:871689213001765046 be...

reinier_vanderh · 10-03-2018

We're logging our requests to Loggly with the messageLogging policy. This is what it looks like: messageLogging false true logs-01.loggly.com [xxxxx tag="xxxx"] {messageLogging} 6514 TCP false true false true INFO 0 Apigee automatically ad...

reinier_vanderh · 01-31-2019

Thank you for the clear answer, that explains our problem exactly.

reinier_vanderh · 10-03-2018

Thank you for your response.We're on edge SaaS.

reinier_vanderh · 08-19-2018

If the URL https://login.microsoftonline.com/{tennantId}/discovery/v2.0/keys does not work, this is an issue in your Azure AD configuration, not in Apigee.

reinier_vanderh · 08-15-2018

According to the docs:Property values can only be literals. You cannot set values using variables.The only solution I see would be to create multiple targetEndpoints using a routerule based on environment. environment.name === 'dev' TargetEndpoint1

reinier_vanderh · 08-15-2018

Hi Raj,No I did not. You can check if the endpoint is correct by browsing to it in your browser. This should return a JSON body with the keys in it.

My Stats

reinier_vanderh's Bio

Badges reinier_vanderh Earned

Recent Activity

XMLtoJSON policy rounds long numbers

Messagelogging syslog is not sending milliseconds correctly

Re: XMLtoJSON policy rounds long numbers

Re: Messagelogging syslog is not sending milliseconds correctly

Re: Validating JWT generated from Azure AD

Re: timeout in Apigee Target endpoint using HTTPTargtConnection Properties

Re: Validating JWT generated from Azure AD