Power Automate

Problem with Custom Connector. OAuth 2 access token refresh failed. Client ID and secret sent in form body

(1) Share

Report

Posted on by ecrevisse

111

Hi Everyone,

we have problem with our custom connector. When i try used new connection, i received below problem.

Failed to refresh access token for service: aad. Correlation Id=xxx. OAuth 2 access token refresh failed. Client ID and secret sent in form body.. Response status code=Unauthorized. Response body: {"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.

Honeslty, i don't know what happened. Client secret ID is correct 🙂 Have you had a similar problem?

Damian

Categories:

Connector development

I have the same question (0)

All responses (3)

Answers (0)

TomMoody 115 on at

Like (0)

Report

Hey Damian,

So that I can attempt to recreate the problem can you please tell me what type of identity provider you are using?
I have a feeling it is AAD, if so can you send some screenshots of your accompanying App Registration in Entra ID?

Source: Authenticate your API and connector with Microsoft Entra ID | Microsoft Learn

Was this reply helpful? Yes No
Suggested answer

hasnainhaider68 47 on at

Like (0)

Report

For issues related to expired access tokens, user connections, or multi-factor authentication (MFA), please follow these steps:

1. Open an incognito window and log in as the user. This will trigger an Authenticator notification to the app, refreshing the access token.

2. Log in, navigate to the connections, and reconfigure any broken connections. Then, access Power Apps or any other solution and perform a hard refresh of the browser. The issue should be resolved.

The problem arises due to inactive or outdated tokens. Refreshing the token through the Authenticator app will resolve the issue.
Please let me know when this is complete.

Was this reply helpful? Yes No
Andy_Moyer 29 on at

Like (0)

Report

hasnainhaider68 I'm having a similar problem. I've read your reply but how do I force the user to refresh their tokens as part of their daily workflow and not need to reach out and do the steps below? I've tried having them go to Outlook365, log out and log in but that doesn't seem to refresh the token associated to the Power App calling the Power Flow.

Was this reply helpful? Yes No