Different behavior in different org for validation

[#1]

When passing form param to apigee proxy to get access token, if say value of client_id contains white space in beginning or end, it raise desired error.

But in other organisation, those white space get trimmed and validation passes successfully.

curl -X POST -H "Accept: application/json" -H "Cache-Control: no-cache" -H "Content-Type: application/x-www-form-urlencoded" -d 'client_id= abc233&client_secret= abc&code=...&grant_type=authorization_code&redirect_uri=http://httpbin.org/get' "http://.../../token"

Is there any global setting for this kind of behavior?

Thanks,

[DChiesa]

> it raise desired error.

What is the "IT" that is raising an error? What is doing the validation?

[#3]

@Dino

Well, 'IT' means GenerateAccessToken / GenerateAuthorizationCode etc.. operations.

[amar333n]

@Nitesh

May be you are using different versions of APIGEE for diffrent organzation.

you can find out the version of Apigee software by navigating to "/buildInfo" once you are logged in.

[#5]

@Amar N

Like I have dev and qa environment. After logging, then lets say I have following url:

https://enterprise.apigee.com/platform/testqa/

https://enterprise.apigee.com/platform/testdev/

and appending /buildInfo gives 404 not found.

[DChiesa]

@Nitesh Is this a real problem? Maybe you should just "not use spaces" ? I mean, isn't the workaround pretty easy? Is it worthwhile spending any further time exploring this?

[#7]

@Dino

What you are saying is happy scenario. My concern is when end users pass client_id with space, it get caught in one environment, but same is not true for other environment.

For QA ppl, if they are testing in one env, ang getting expected output, and they would expect same out put in other environment as well for same input.

I was thinking of handling all those white space scenario in javascript but thought if its already there in one env then I might be missing some configuratoin thing for other environment.