Error when connecting via Oauth2 to Yandex.Disk

Questions
,
1

When connecting via Oauth2 to Yandex.Disk, I get an error - UnauthorizedError.

I filled out everything as described.
Please help with authorization.
Thank you.

What is the error message (if any)? UnauthorizedError

Please share the workflow

(Select the nodes and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow respectively)

Share the output returned by the last node

<!-- {"status":"rejected","reason":{"message":"401 - {\"message\":\"Не авторизован.\",\"description\":\"Unauthorized\",\"error\":\"UnauthorizedError\"}","name":"Error","stack":"Error: Request failed with status code 401\n at createError (/usr/local/lib/node_modules/n8n/node_modules/axios/lib/core/createError.js:16:15)\n at settle (/usr/local/lib/node_modules/n8n/node_modules/axios/lib/core/settle.js:17:12)\n at IncomingMessage.handleStreamEnd (/usr/local/lib/node_modules/n8n/node_modules/axios/lib/adapters/http.js:269:11)\n at IncomingMessage.emit (node:events:525:35)\n at IncomingMessage.emit (node:domain:489:12)\n at endReadableNT (node:internal/streams/readable:1358:12)\n at processTicksAndRejections (node:internal/process/task_queues:83:21)"}} -->

yandex_disk_oauth2_2
yandex_disk_oauth2_21277×864 89.6 KB

yandex_disk_oauth2_1
yandex_disk_oauth2_11898×1960 149 KB

Information on your n8n setup

  • **n8n version:**0.194.0
  • Database you’re using (default: SQLite):
  • **Running n8n with the execution process [own(default), main]:**main
  • **Running n8n via [Docker, npm, n8n.cloud, desktop app]:**Docker
2

Hey @asuhan,

It looks like Yandex is not happy with the credentials being used, Looking at your OAuth credential screenshot you don’t have any scopes set. Does Yandex not require any?

3

Good afternoon, Jon. Scopes are required, but they are already provided to the application.
If I connect using a debug token, i.e. manually insert it into the request, the request passes.
There must be some problem with getting the token itself in Credential.

image
image1395×831 67.3 KB

4

Hey @asuhan,

I suspect the debug token is already authenticated using the scopes required which is why that works. Can you add the scopes to the credential and see if that helps, Normally just adding scopes to the application isn’t enough and the application authenticating also needs to confirm what scopes will be needed for the user authenticating but it could be that Yandex doesn’t work that way.

Does Yandex need anything anything else special when authenticating like an additional header to be sent? I am not aware of any issues with the OAuth implementation at the moment so I suspect it is going to be something Yandex specific.

5

With scopes in credentials, it does not skip at all…

yandex_disk_oauth2_scopes
yandex_disk_oauth2_scopes1473×853 84.1 KB

6

Hey @asuhan,

We tend to split the scopes with spaces so that could be an issue, What does the error message say there?

7

I separated scopes with spaces, the error is the same.
“status”: “rejected”,
{ “reason”: {
“message”: “401 - {“message”: “Not Authorized.”, “description”: “Unauthorized”, “error”: “UnauthorizedError”}”
{ “name”: “Error”,

8

Hey @asuhan,

Have you tried the other authentication method? Do you have a link to the OAuth documentation for Yandex?

9

Good day, Jon. Accessing the API - API. Yandex.Disk API

10

Hey @asuhan,

That is interesting, They mention on that page that they expect Authorization: OAuth xxxyyyzzz but we send Authorization: Bearer xxxyyyzzz I wonder if they only support that header value or if they support bearer as well :thinking:

11

Maybe that’s why it works with the debug token, because there I manually wrote “OAuth y0_AgAAAAADDkqcAAhv9wAAAADPu…”

12

I can’t see anything to suggest they don’t support it but I would be surprised…

This is all a bit odd, I may have to make an account and see what is going on.

13

I would be very grateful to you, Jon. I hope you have time for this.

14

Greetings, Jon!
I recently tried to connect Yandex API using OAuth and got the same issues you are discussing here. Maybe there is a way to get around this limitation in the meantime, any news?
In Postman, there is an option to set the header prefix. This solves an exceptional situation with Yandex API. Maybe there is a similar solution in n8n that I haven’t seen yet.
Please guide if you know what can help me to keep getting the token automatically and using it in requests. Any hints would be appreciated.

15

Hi everyone! Any updates?

I’m trying to use the Yandex API and am experiencing the same issue…