/oauth2/token/ suddenly returns 403

Question

I have this webapp that has been doing reverse geolocation for years, get an oauth token and then requesting a reserve-geocode.

Now, starting jan 7, the /oauth2/token/ suddenly returns a 403 forbidden (clearly using valid client-id + secret, double triple checked).

Now, when running the exact same request (ur, client-id, client-secret, etc, etc) using postman a oauth-token is returned successfully..

What can this be? Has my ip-address been blocked?

I generated a new client-id + secret, same issue.

RobVerdeul · Answer

Somebody from Esri or Arcgis be able to help me out here?

RobVerdeul · Answer

Well, the arcgis portal is difficult to navigate for me. But afaikt i see nothing there indicating that my account is blocked or expired or whatever.

Codewise on my end nothing, really nothing has changed on jan 7. And i did check the postman request agina and again against what i send from my php webapp.

Contacting tech support is not an option for me, i am on a free account. 🙂

John-Foster · Answer

there isn't enough information here to determine your issue, someone would have to review the code. It is strange that a request using Postman would produce different results for the exact same request with your code, so you really have to review all the parameters you are sending to the end point, there must be something different. Did you review the doc at https://developers.arcgis.com/rest/users-groups-and-items/token/ ? I don't think there is any special about Jan 7 for the backend, but check your account status maybe something changed on your account around that date?

are you able to contact technical support for help?