Issue with MS Oauth2 on n8n cloud

Questions
,
21

Hey @jacobprecht,

From what we currently understand from more testing recreating the credential will work and will use the new secret but existing credentials will still use the old one. Now looking to see what we can do around this.

22

Does anyone fancy testing again to see if the message changes or if it works?

23

Still the same error for me when I ‘reconnect’. Adding new credentials did work though.

{"error":"invalid_client","error_description":"AADSTS7000215: Invalid client secret provided. Ensure the secret being sent in the request is the client secret value, not the client secret ID, for a secret added to app 'aad843ca-42a7-4219-a3f9-91bcf621d795'. Trace ID: 2fa7cff3-addf-4533-aefe-7937cbaa4e00 Correlation ID: 2204de1e-eda6-4286-a7e0-4b5f5dbcee30 Timestamp: 2023-12-01 17:42:41Z","error_codes":[7000215],"timestamp":"2023-12-01 17:42:41Z","trace_id":"2fa7cff3-addf-4533-aefe-7937cbaa4e00","correlation_id":"2204de1e-eda6-4286-a7e0-4b5f5dbcee30","error_uri":"https://login.microsoftonline.com/error?code=7000215"}
24

So it sounds like at the moment the best option is to recreate credentials if reconnecting is not working.

We will continue to investigate this issue.

25

Hi Jon - I have a client I support that is not able to add new credentials i.e. the workaround above.

Are you able to take a look there - this domain is ***

26

Hey @Rob_Hopkins,

Right now the only option is to add the credential again, We are still looking to see if the credential is using the old token because of a cache on our side or if there is something Microsoft have in the token.

Does the client get an error when adding a new credential? If they get the same token issue I can fix that fairly quickly.

27

Hi Jon

Yes, adding a new credential here is giving the same error:

{"error":"invalid_client","error_description":"AADSTS7000215: Invalid client secret provided. Ensure the secret being sent in the request is the client secret value, not the client secret ID, for a secret added to app 'aad843ca-42a7-4219-a3f9-91bcf621d795'. Trace ID: ae7a54d4-cc99-4c02-b704-f02bf8512100 Correlation ID: a5718af5-321c-4de8-9995-15fcd9d69ea9 Timestamp: 2023-12-05 08:19:26Z","error_codes":[7000215],"timestamp":"2023-12-05 08:19:26Z","trace_id":"ae7a54d4-cc99-4c02-b704-f02bf8512100","correlation_id":"a5718af5-321c-4de8-9995-15fcd9d69ea9","error_uri":"https://login.microsoftonline.com/error?code=7000215"}
28

Hey @Rob_Hopkins,

I have just triggered another restart of their instance, Can you try again now?

29

That looks like it! Thanks - sorry, I had not performed the update/restart steps first.

Thanks

1 Like
30

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.