Vor Kurzem aufgerufene Suchen
Keine vor kurzem aufgerufene Suchen
Proxy error: UnprocessableEntity, Failed to get installation and oauth information for app
Gepostet 20. Jan. 2022
I have been guided here by Zendesk support, I am receiving the error Proxy error: {:code=>"UnprocessableEntity", :status=>"422", :title=>"Unprocessable Entity", :message=>"Failed to get installation and oauth information for app."} when I attempt to create a request to a 3rd party server, I have followed your extensive guide but still recieving the above.
2
48
48 Kommentare
Christopher Kennedy
It looks like your OAuth provider is not providing a refresh token on successful authorization. Can you please refer to their documentation for more info on how to ensure it sends a refresh token along with the access token?
0
Nicklas Hintze
Hi,
We are having same issues with an app being developed for one of our customers.
If I bypass the secure setting/proxy and manually enter an access token for the app then the requests go through and we get data.
However, when we try to go via the secure proxy we get the same error with
In the app settings we have successfully logged in and it is showing a green check marker next to the Oauth login.
Everything in manifest.json also looks correct
And when checking Network in the browsers Developer Tools I can see that it is correctly including Bearer {{setting.token}} for Authorization.
Would appreciate some assistance in checking logs as I can't really see anything wrong in the app itself for this.
0
Christopher Kennedy
Sorry for the confusion. I created a ticket work with you one-on-one. I have a reply with next steps there.
0
Andrew Runciman
Hi Chris, Can I confirm that you are able to look at the logs to help us pinpoint our issue. The issue that Parth Patel raised is different to ours. I can confirm that we have tried all of the steps that Jerry has posted above. We have also added the additional scope of offline_access. Our integration is Auth0. Again, it is working as expected once the app is installed, but we see the 422 error at a point where we think the token way not refresh (although I cant confirm unless someone can look at the logs). Again, an example timestamp would be 2025-03-24T15:54:22. We also saw the issue again this morning. Reinstalling the app fixes the issue temporarily.
0
Christopher Kennedy
No problem. I'm glad to hear it's working for you!
Best,
Chris Kennedy | Developer Advocate
0
Parth Patel
That was it, dont know how i missed that, thank you
0
Andrew Runciman
I will take a look at the docs and see if the offline_access is also required for Auth0
0
Andrew Runciman
Hi Chris, Can you check the logs for our issue - we are using OAuth. Regards Andy
0
Christopher Kennedy
Thanks for the info. In our logs I can see that our OAuth connection service fails to refresh because it did not receive a refresh token from NinjaOne on the initial authorization. To allow a refresh token to be returned, can you please include an
offline_access
scope in the app's manifest? NinjaOne's docs note that this scope is required for them to return a refresh token.Best,
Chris Kennedy | Developer Advocate
1
Parth Patel
I was able to authenticate upon initial load/install of the app but I don't have any way to see logs when it goes for refresh token.
This worked successfully 5 hours ago. and when i came back to it I am getting this error. so I am assuming the refresh token failed, the expires_in key is in the response from the token endpoint.
Please see link below
https://app.ninjarmm.com/apidocs-beta/authorization/flows/authorization-code-flow
ZAF client Support App Function:
async function getDevices() {
if (!token) {
console.log("Failed to obtain access token");
return;
}
try {
return await client.request({
url: "https://app.ninjarmm.com/api/v2/devices-detailed",
type: "GET",
headers: { Authorization: "Bearer {{setting.token}}" },
secure: true,
});
} catch (error) {
console.error("Error fetching devices:", error);
}
}
Manifest portion regarding oauth:
"parameters": [
{
"name": "token",
"type": "oauth"
}
],
"oauth": {
"response_type": "code",
"client_id": "************************",
"client_secret": "**********************************",
"authorize_uri": "https://app.ninjarmm.com/ws/oauth/authorize",
"scope": "control monitoring management",
"access_token_uri": "https://app.ninjarmm.com/ws/oauth/token"
},
0
Melden Sie sich an, um einen Kommentar zu hinterlassen.