Getting error in acquiring access token

One of our consumer is calling oauth proxy which we created in APIGEE to get the access token. The issue here is, whenever the consumer hits the proxy url for

first time they are getting the below errors,

  Warning  Default-thread-4  WARNING
*** WARNING *** java.net.SocketTimeoutException: connect timed out when posting
to https://somehost/v1/oauth/token.  

Info  Default-thread-4  ***Script: test123 Cannot acquire token

provided we are giving the clientid and client secret to them to access the proxy.

"But the same is working . ie generating access token when they hit the same url for the second time without making any change in the request."

Please let me know if anyone is aware of this issue earlier.??

@Divya Achan, @Anil Sagar

@Dino,@Diego Zuluaga,@Sandeep Murusupalli,@Paul Mibus,@Prithpal Bhogill,

@dj1,@Steven Wolfe,@Sean Davis,

Sorry to add so may reputed apigee member for the answer, as its very urgent , please please do provide some suggestion or answer ..:)

0 4 356
4 REPLIES 4

@Ankit Dwivedi , Is above issue still reproducible ? Are you on cloud / onpremises ? Is it trial or paid org ?

Ya @Anil Sagar , Its paid org .

every time we try to hit for first time we are getting this error ,when we hit second time it is working fine ..

we are on cloud...

Don't know why this is happening.???

Former Community Member
Not applicable

Can u share the complete CURL command i.e. verb, headers, params etc (you can fake the values) that the consumer of the OAuth proxy is issuing? Also can you share what policies are present in the proxy? Best if you can share the proxy bundle here.

feels like a network issue. Is it reproducible from multiple different network locations? IS it possible the consumer in this case is running on a network that is mis-behaving ?

Have you used trace in the Apigee UI to check the behavior of the OAuth2 proxy? What is it doing? Is it calling to a remote service that is perhaps timing out?

You need to perform more diagnostics.