With interruptions over the past two days, two different LinkedIn applications began to receive 999 rejection requests. Along with this, I get: "reason-code = 1,2,1" as the title. In particular, this was recorded from the 3rd stage of the oAuth process (communication with https://www.linkedin.com/uas/oauth2/accessToken ), however, making POST requests to the sharing endpoint also failed, but I still did not capture the HTTP response code and data for these failures.
These two applications are live and test sites for the same platform, launching different servers, different IP addresses, different client identifiers, and two applications are tied to two different users (although I am the administrator of both), One thing they have together, is that they are both hosted on Linode.
Locally (with another client id / app) integration works without problems. If I use the client ID of the test application locally (with the callback URLs added), the integration works without problems.
It seems choppy. Over the past two days, the API has had a high level of POST request errors. As well as intermittent oAuth connection denial complaints.
On the developer's website, I see that the applications are well suited to use.
Does anyone know what this particular error with reason code 1,2,1 refers to? LinkedIn's developer website cites error 999, but it seems to be limited so that only registered affiliate program members can access them. And is there any approach to prevent this error. Some other questions indicate that the 999 response code began to occur through LinkedIn, blocking various cloud providers, however this does not seem to explain why this is intermittent.
source
share