Issue with MS Oauth2 on n8n cloud

Questions
,
1

Seems to be an issue with the Oauth2 app for Microsoft on n8n cloud.

image
image803Ă—202 10.4 KB

Credentials were working fine but now died.

Information on your n8n setup

  • n8n version: 1.18
  • Running n8n via (Docker, npm, n8n cloud, desktop app): n8n cloud
2

It looks like your topic is missing some important information. Could you provide the following if applicable.

  • n8n version:
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app):
  • Operating system:
3

I don’t mind these automated messages. But they are too aggressive.
For n8n cloud we don’t know what the answers are. (of course I can make an educated guess for most)
So please make these a bit less aggressive :slight_smile:

1 Like
4

I have the same issue with MS Driver Auth

5

It does say “if applicable” but I will update the wording…

We are also aware of the issue and should have it resolved shortly.

1 Like
6

Hi Jon, should we expect information like this to show on your status page? status.n8n.cloud Would have save a lot of investigation this morning

FYI, I’ve just restarted as you requested a user to on a similar thread but the problem persists. (v1.18)

7

Hey @Rob_Hopkins,

Welcome to the community :cake:

Putting on the status page would have been a good idea, Sadly I have not had a chance to do that yet but we believe the issue should be resolved now.

Can you share your cloud username and the error you are seeing?

8

Thanks for the welcome.

The error I see is the same as the original post.

The owner account is - I couldn’t see a DM option, please let me know once you have these and I’ll edit the comment.

Thanks

9

Perfect thanks.

1 Like
10

I have the same issue. Cloud instance name “informeren”
MS login account verified and no keys are expired

Error from node:

ERROR: Client authentication failed (e.g., unknown client, no client authentication included, or unsupported authentication method).

Client authentication failed (e.g., unknown client, no client authentication included, or unsupported authentication method).

Details

Time

1.12.2023 13.06.17

HTTP Code

EAUTH

Stack

NodeApiError: Client authentication failed (e.g., unknown client, no client authentication included, or unsupported authentication method).
at Object.microsoftApiRequest (/usr/local/lib/node_modules/n8n/node_modules/n8n-nodes-base/dist/nodes/Microsoft/OneDrive/GenericFunctions.js:29:15)
at runMicrotasks ()
at processTicksAndRejections (node:internal/process/task_queues:96:5)
at Object.execute (/usr/local/lib/node_modules/n8n/node_modules/n8n-nodes-base/dist/nodes/Microsoft/OneDrive/MicrosoftOneDrive.node.js:146:44)
at Workflow.runNode (/usr/local/lib/node_modules/n8n/node_modules/n8n-workflow/dist/Workflow.js:652:28)
at /usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/WorkflowExecute.js:592:53


![](https://informeren.app.n8n.cloud/icons/n8n-nodes-base/dist/nodes/Microsoft/OneDrive/oneDrive.svg)

Microsoft OneDrive

Execute node

Parameters

[
Docs
](https://docs.n8n.io/integrations/builtin/app-nodes/n8n-nodes-base.microsoftonedrive/?utm_source=n8n_app&utm_medium=node_settings_modal-credential_link&utm_campaign=n8n-nodes-base.microsoftOneDrive)

Error as reported in MS Entra:

Failure reason

The provided client secret keys for app '{identifier}' are expired. Visit the Azure portal to create new keys for your app: https://aka.ms/NewClientSecret, or consider using certificate credentials for added security: https://aka.ms/certCreds.

Additional Details

Developer error - the app is attempting to sign in without the necessary or correct authentication parameters.
11

Hey @jacobprecht,

Welcome to the community :tada:

Thanks, We have rotated the key now so it should be working. We have done some testing and restarting the instance has helped for us so just trying to see why it wouldn’t do the same for others.

As you are on a pre v1 version it would be worth upgrading first.

12

Thx. I will upgrade soon, but for now it is not possible. Som heavy testing must be done first.

It still fails after instance restart. The error seen in MS is the same. I see 100% succesfull attempts from IP 85.204.132.69 and 100% failing attempts from IP 20.218.202.73 since yesterday.

13

Can you try and connect now?

14

I am still having the problem. I have restarted too.

FYI, it’s not all credentials that fail, but those that do have the same error.

My personal email will reconnect, although it did earlier this morning too. But others, in the same azure organisation, do not.

15

I have just restarted instance and retried. It still fails

16

Hey @jacobprecht,

We have also just restarted instances that we believe were seeing the issue which should have resolved it. I will do some more digging.

1 Like
17

Hi Jon - how is it looking?

To confirm, my error is

{"error":"invalid_client","error_description":"AADSTS7000222: The provided client secret keys for app 'aad843ca-42a7-4219-a3f9-91bcf621d795' are expired. Visit the Azure portal to create new keys for your app: https://aka.ms/NewClientSecret, or consider using certificate credentials for added security: https://aka.ms/certCreds. Trace ID: 638a137f-92f6-465c-9fd2-ba9058a80200 Correlation ID: 80abfdac-ce97-4824-abcc-654855b13f00 Timestamp: 2023-12-01 14:40:38Z","error_codes":[7000222],"timestamp":"2023-12-01 14:40:38Z","trace_id":"638a137f-92f6-465c-9fd2-ba9058a80200","correlation_id":"80abfdac-ce97-4824-abcc-654855b13f00","error_uri":"https://login.microsoftonline.com/error?code=7000222"}

I think the trace_id and correlation_id are different every time, but maybe are of some use to you.

1 Like
18

Got fixed in my instance when setting up the credentials again

19

Hey @Rob_Hopkins,

We are now trying to work out why some instances are not picking up the new secret key that we deployed.

20

I have just created new credentials in the same instance and it works. It did not succeed earlier today