cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Knots
Frequent Visitor

Custom Connector - OAuth2 - Old refresh token used

We've created a custom connector for Exact Online, but are having issues with the access tokens. Everything works, but at some point the connection states it "Can't sign in" and you'll need to fix the connection before you can use it again. When checking the detail of that connection, it states:

 

 

 

Failed to refresh access token for service: oauth2. Correlation Id=..., UTC TimeStamp=..., Error: OAuth 2 access token refresh failed. Client ID and secret sent in form body.. Response status code=Unauthorized. Response body: {"error":"unauthorized_client","error_description":"Old refresh token used."}

 

 

 


The authentication type of the custom component is set to OAuth2. The identity provider is the Generic OAuth2 one. It uses the "Authorization Code" flow. We've tried the "Implicit" one as well to no avail.

 

Since the connection works initially, the authorization and token URL seem to be correct. We can authenticate and use the connection in an, e.g. Canvas App.
According to the documentation, the refresh URL is the same as the token URL:

 

 

 

../api/oauth2/token

 

 

 


If the token would expire once a month or so, I could live with it, but the token expires after just 10 minutes...

Can anyone tell me why an old refresh token is used? Is the token simply not updated after refreshing it? Is it refreshing multiple times simultaneously, in which case the second call probably results in the error?

What am I missing?

 

edit: added additional information regarding the authentication method.

50 REPLIES 50

The documentation says that with each refresh, a new acces code is generated:

Knowledge Base - Step 4. Obtain new access tokens (exactonline.com)

Yes, I meant the refresh token. The custom connector seems to be refreshing the access token correctly (if using only one connection), but apparently does not refresh the refresh token (correctly). That's my interpretation, because the refresh token becomes invalid after a month.

Piebe_Post
Advocate I
Advocate I

In that scenario, you still need to store the new refresh token that has just been "manually" refreshed somewhere inside Power Platform's connection settings. 

Yep, and that's not possible as far as I know. And that leads as back to building a custom proxy, unfortunately. 

DerekH_AU
Frequent Visitor

A couple of ways I have gotten around authentication issues (albeit not for an oauth issue that the platform should be handling, but power automate is pretty rigid in its implementation of oauth, or their interpretation of the standard)...

Doing a poll/keep alive, even just a list records or some other ping on the connection (in my case the token was only valid for 60 mins, but the refresh tokens were valid for much longer so getting my reference data every 24 hours was enough).

For a different type of auth, I configured all my requests to include an extra header parameter which allowed me to pass through the required auth token. I used the new custom connector code to modify the request to change that value to the required auth header for the request. You'd still need to manage getting/refreshing the token (likely by custom code in the connector for a custom request), and store the token somewhere (or pass it back out with each response so it can be saved if changed) and then pass it through on each request. Obviously this isn't ideal as it exposes the token to anyone that can see the flow, although you can mark the inputs/outputs as secret so it obfuscates them. This might be better/easier than doing a full proxy on azure.

I don't recall the issue back when I added to this thread but from memory mine was just a symptom of another issue like an incorrect refresh URL (and it was connecting to a different 3rd party service).

 

I don't know and have never used the Exact API you guys are referring to, but power automate might also struggle with their rule around not being able to request a new token before the existing token is at least 9 mins and 30 seconds old. The refresh token is valid for 30 days, so it should be able to refresh that within the 30 day window. This part is very similar to the API I am calling, and it does manage to handle getting the refresh tokens. If you haven't already, it might be worth reaching out to both Microsoft Support and Exact support to see if you can work out why they are expiring. I did log my issue and that did somewhat help point me in the direction to resolve my issue.

 

Also just confirm when setting up the auth you are using /api/oauth2/auth for your authorisation URL and /api/oauth2/token for both your Token and Refresh URLs, because I have a feeling that was why mine weren't refreshing (the wrong URLs).

 

Hope that helps and good luck.

Hi @DerekH_AU,

 

Thanks for the extensive reply. Could you show an example of how the custom code works in the custom connector? I'm not familiar with it.

Didn't think about the possibility for using a connector code but if that gives the possibility to get an access token from an Azure Key Vault, which may be refreshed by an external application, that might be exactly what I'm looking for!

 

Thank you so much for your input!

Got it 😎

 

 

using System.Net.Http;
using System.Threading.Tasks;
using Microsoft.Azure.WebJobs.Host;
using Newtonsoft.Json.Linq;

public class Script : ScriptBase
{
    public override async Task<HttpResponseMessage> ExecuteAsync()
    {
        // Log instance ophalen
        var log = this.Context.Logger;

        // Verwijder de bestaande Authorization header
        this.Context.Request.Headers.Remove("Authorization");

        // URL van de GET API
        string apiUrl = "https://prod-208.westeurope.logic.azure.com:443/workflows/[....]";

        // Maak een nieuwe HttpRequestMessage voor de API-aanroep
        var tokenRequest = new HttpRequestMessage(HttpMethod.Get, apiUrl);

        // Voer het GET-verzoek uit via Context.SendAsync
        var tokenResponse = await this.Context.SendAsync(
            request: tokenRequest,
            cancellationToken: this.CancellationToken).ConfigureAwait(false);

        // Controleer of het verzoek succesvol was
        if (tokenResponse.IsSuccessStatusCode)
        {
            // Lees de inhoud van de respons
            string tokenContent = await tokenResponse.Content.ReadAsStringAsync();
            var token = tokenContent.ToString();

            // Voeg de nieuwe Authorization header toe
            this.Context.Request.Headers.Add("Authorization", "Bearer " + token);

            // Log de Authorization header
            log.LogInformation("Authorization header set to: Bearer " + token);
        }
        else
        {
            // Log een foutmelding als het verzoek niet succesvol was
            log.LogError($"Failed to make GET request. Status code: {tokenResponse.StatusCode}");
            return new HttpResponseMessage(System.Net.HttpStatusCode.InternalServerError)
            {
                Content = new StringContent("Failed to retrieve token.")
            };
        }

        // Log alle headers
        foreach (var header in this.Context.Request.Headers)
        {
            var headerValue = string.Join(", ", header.Value);
            log.LogInformation($"Header: {header.Key} = {headerValue}");
        }

        // Stuur het aangepaste verzoek door en verkrijg de respons
        var response = await this.Context.SendAsync(
                request: this.Context.Request,
                cancellationToken: this.CancellationToken)
            .ConfigureAwait(false);
        
        return response;
    }
}

 

This custom code makes a get request that retrieves the actual access token. The authentication type of the custom connector is changed to "No authentication".

 

Obviously, an additional setup is needed to refresh and store access tokens each 10 minutes.

Very interesting! But how do you do the initial login then, via the custom connector you already had? Keep us posted!

I have a separate Azure Functions that I already created as a proxy for webhooks from Exact Online, as the custom connector cannot handle webhooks directly from Exact Online (for some reason I don't remember anymore). I extend this function to store access tokens and refresh tokens in the Key Vault and repeat this action every 9:30 minutes.

ah ok. I also tried webhooks, but it indeed doesn't work with the custom connector. The connector requires an additional header I believe, which Exact doesn't provide.

 

My options are very limited, because I don't have a Power Apps subscription (yet). It is not feasible for us yet.

Helpful resources

Announcements

Win free tickets to the Power Platform Conference | Summer of Solutions

We are excited to announce the Summer of Solutions Challenge!    This challenge is kicking off on Monday, June 17th and will run for (4) weeks.  The challenge is open to all Power Platform (Power Apps, Power Automate, Copilot Studio & Power Pages) community members. We invite you to participate in a quest to provide solutions to as many questions as you can. Answers can be provided in all the communities.    Entry Period: This Challenge will consist of four weekly Entry Periods as follows (each an “Entry Period”)   - 12:00 a.m. PT on June 17, 2024 – 11:59 p.m. PT on June 23, 2024 - 12:00 a.m. PT on June 24, 2024 – 11:59 p.m. PT on June 30, 2024 - 12:00 a.m. PT on July 1, 2024 – 11:59 p.m. PT on July 7, 2024 - 12:00 a.m. PT on July 8, 2024 – 11:59 p.m. PT on July 14, 2024   Entries will be eligible for the Entry Period in which they are received and will not carryover to subsequent weekly entry periods.  You must enter into each weekly Entry Period separately.   How to Enter: We invite you to participate in a quest to provide "Accepted Solutions" to as many questions as you can. Answers can be provided in all the communities. Users must provide a solution which can be an “Accepted Solution” in the Forums in all of the communities and there are no limits to the number of “Accepted Solutions” that a member can provide for entries in this challenge, but each entry must be substantially unique and different.    Winner Selection and Prizes: At the end of each week, we will list the top ten (10) Community users which will consist of: 5 Community Members & 5 Super Users and they will advance to the final drawing. We will post each week in the News & Announcements the top 10 Solution providers.  At the end of the challenge, we will add all of the top 10 weekly names and enter them into a random drawing.  Then we will randomly select ten (10) winners (5 Community Members & 5 Super Users) from among all eligible entrants received across all weekly Entry Periods to receive the prize listed below. If a winner declines, we will draw again at random for the next winner.  A user will only be able to win once overall. If they are drawn multiple times, another user will be drawn at random.  Individuals will be contacted before the announcement with the opportunity to claim or deny the prize.  Once all of the winners have been notified, we will post in the News & Announcements of each community with the list of winners.   Each winner will receive one (1) Pass to the Power Platform Conference in Las Vegas, Sep. 18-20, 2024 ($1800 value). NOTE: Prize is for conference attendance only and any other costs such as airfare, lodging, transportation, and food are the sole responsibility of the winner. Tickets are not transferable to any other party or to next year’s event.   ** PLEASE SEE THE ATTACHED RULES for this CHALLENGE**

Celebrating the June Super User of the Month: Markus Franz

Markus Franz is a phenomenal contributor to the Power Apps Community. Super Users like Markus inspire others through their example, encouragement, and active participation.    The Why: "I do this to help others achieve what they are trying to do. As a total beginner back then without IT background I know how overwhelming things can be, so I decided to jump in and help others. I also do this to keep progressing and learning myself." Thank you, Markus Franz, for your outstanding work! Keep inspiring others and making a difference in the community! 🎉  Keep up the fantastic work! 👏👏 Markus Franz | LinkedIn  Power Apps: mmbr1606  

Copilot Cookbook Challenge | Week 1 Results | Win Tickets to the Power Platform Conference

We are excited to announce the "The Copilot Cookbook Community Challenge is a great way to showcase your creativity and connect with others. Plus, you could win tickets to the Power Platform Community Conference in Las Vegas in September 2024 as an amazing bonus.   Two ways to enter: 1. Copilot Studio Cookbook Gallery:  https://aka.ms/CS_Copilot_Cookbook_Challenge 2. Power Apps Copilot Cookbook Gallery: https://aka.ms/PA_Copilot_Cookbook_Challenge   There will be 5 chances to qualify for the final drawing: Early Bird Entries: March 1 - June 2Week 1: June 3 - June 9Week 2: June 10 - June 16Week 3: June 17 - June 23Week 4: June 24 - June 30     At the end of each week, we will draw 5 random names from every user who has posted a qualifying Copilot Studio template, sample or demo in the Copilot Studio Cookbook or a qualifying Power Apps Copilot sample or demo in the Power Apps Copilot Cookbook. Users who are not drawn in a given week will be added to the pool for the next week. Users can qualify more than once, but no more than once per week. Four winners will be drawn at random from the total qualifying entrants. If a winner declines, we will draw again at random for the next winner.  A user will only be able to win once. If they are drawn multiple times, another user will be drawn at random. Prizes:  One Pass to the Power Platform Conference in Las Vegas, Sep. 18-20, 2024 ($1800 value, does not include travel, lodging, or any other expenses) Winners are also eligible to do a 10-minute presentation of their demo or solution in a community solutions showcase at the event. To qualify for the drawing, templates, samples or demos must be related to Copilot Studio or a Copilot feature of Power Apps, Power Automate, or Power Pages, and must demonstrate or solve a complete unique and useful business or technical problem. Power Automate and Power Pagers posts should be added to the Power Apps Cookbook. Final determination of qualifying entries is at the sole discretion of Microsoft. Weekly updates and the Final random winners will be posted in the News & Announcements section in the communities on July 29th, 2024. Did you submit entries early?  Early Bird Entries March 1 - June 2:  If you posted something in the "early bird" time frame complete this form: https://aka.ms/Copilot_Challenge_EarlyBirds if you would like to be entered in the challenge.   Week 1 Results:  Congratulations to the Week 1 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Copilot Cookbook Gallery:Power Apps Cookbook Gallery:1.  @Mathieu_Paris 1.   @SpongYe 2.  @Dhanush 2.   @Deenuji 3.  n/a3.   @Nived_Nambiar  4.  n/a4.   @ManishSolanki 5.  n/a5.    n/a

Your Moment to Shine: 2024 PPCC’s Got Power Awards Show

For the third year, we invite you, our talented community members, to participate in the grand 2024 Power Platform Community Conference's Got Power Awards. This event is your opportunity to showcase solutions that make a significant business impact, highlight extensive use of Power Platform products, demonstrate good governance, or tell an inspirational story. Share your success stories, inspire your peers, and show off some hidden talents.  This is your time to shine and bring your creations into the spotlight!  Make your mark, inspire others and leave a lasting impression. Sign up today for a chance to showcase your solution and win the coveted 2024 PPCC’s Got Power Award. This year we have three categories for you to participate in: Technical Solution Demo, Storytelling, and Hidden Talent.      The Technical solution demo category showcases your applications, automated workflows, copilot agentic experiences, web pages, AI capabilities, dashboards, and/or more. We want to see your most impactful Power Platform solutions!  The Storytelling category is where you can share your inspiring story, and the Hidden Talent category is where your talents (such as singing, dancing, jump roping, etc.) can shine! Submission Details:  Fill out the submission form https://aka.ms/PPCCGotPowerSignup by July 12th with details and a 2–5-minute video showcasing your Solution impact. (Please let us know you're coming to PPCC, too!)After review by a panel of Microsoft judges, the top storytellers will be invited to present a virtual demo presentation to the judges during early August. You’ll be notified soon after if you have been selected as a finalist to share your story live at PPCC’s Got Power!  The live show will feature the solution demos and storytelling talents of the top contestants, winner announcements, and the opportunity to network with your community.  It's not just a showcase for technical talent and storytelling showmanship, show it's a golden opportunity to make connections and celebrate our Community together! Let's make this a memorable event! See you there!   Mark your calendars! Date and Time: Thursday, Sept 19th Location: PPCC24 at the MGM Grand, Las Vegas, NV 

Tuesday Tip | Accepting Solutions

It's time for another TUESDAY TIPS, your weekly connection with the most insightful tips and tricks that empower both newcomers and veterans in the Power Platform Community! Every Tuesday, we bring you a curated selection of the finest advice, distilled from the resources and tools in the Community. Whether you’re a seasoned member or just getting started, Tuesday Tips are the perfect compass guiding you across the dynamic landscape of the Power Platform Community.   To enhance our collaborative environment, it's important to acknowledge when your question has been answered satisfactorily. Here's a quick guide on how to accept a solution to your questions: Find the Helpful Reply: Navigate to the reply that has effectively answered your question.Accept as Solution: Look for the "Accept as Solution" button or link, usually located at the bottom of the reply.Confirm Your Selection: Clicking this button may prompt you for confirmation. Go ahead and confirm that this is indeed the solution.Acknowledgment: Once accepted, the reply will be highlighted, and the original post will be marked as "Solved". This helps other community members find the same solution quickly. By marking a reply as an accepted solution, you not only thank the person who helped you but also make it easier for others with similar questions to find answers. Let's continue to support each other by recognizing helpful contributions. 

Reminder: To register for the Community Ambassador Call on June 13th

Calling all Super Users & User Group Leaders   Reminder: To register for the Community Ambassador Call on June 13th—for an exclusive event for User Group Leaders and Super Users! This month is packed with exciting updates and activities within our community.   What's Happening: Community Updates: We'll share the latest developments and what's new in our vibrant community.Special Guest Speaker: Get ready for an insightful talk and live demo of Microsoft Copilot Studio templates by our special guest.Regular Updates: Stay informed with our routine updates for User Groups and Super Users.Community Insights: We'll provide general information about ongoing and upcoming community initiatives. Don't Miss Out: Register Now: Choose the session that fits your schedule best.Check your private messages or Super User Forum for registration links. We're excited to connect with you and continue building a stronger community together.   See you at the call!  

Users online (2,351)