cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Anonymous
Not applicable

Authorization Bearer in Header - Custom Connector

I have created a custom connector that is connecting to a vendor's API.  I have unauthenticated GET methods working, but now am working on some POSTs and am running into an issue with putting "Authorization: Bearer token_value" in the header.  Even on the unauthenticated GET calls, I can see in the request header that "Authorization: Bearer some_token_value" is already there.  I've tried setting the Header in my POST call, but then I get the error: "Message": "Error from ASE: Bad authorization header scheme".

 

I can see that the request header has my token_value and so it appears I'm not allowed to set the header that way.  What is the right way to send my "Authorization: Bearer token_value" to the API?

 

Thank you.

1 ACCEPTED SOLUTION

Accepted Solutions
Anonymous
Not applicable

I've figured this out by learning about making an OpenAPI document describing the interface, and creating a custom connector off of the document.

  1. On the Security tab, select "API Key" for the Authentication type
  2. For "Parameter Label" put whatever you want someone to see when they are creating a Connection off of this Connector...I used "API Key"
  3. "Parameter Name" should be "Authorization" (no quotes)
  4. For "Parameter Location", select "Header"
  5. When you create a Connection off of this Connector, you'll be prompted for your "API Key" (or whatever you used for step 2 above)
  6. Enter "Bearer YOUR_BEARER_TOKEN_VALUE" (no quotes)

This will pass your bearer token to the API successfully.

View solution in original post

39 REPLIES 39
alexco
Advocate I
Advocate I

I have the same issue, did you solve it in the meantime?

Anonymous
Not applicable

I ended up opening a ticket with Microsoft, went back and forth with them a few times, but they never seemed to understand the issue no matter how many times I explained it, so I've had to give up for now.

 Facing the same problem - MS should help us out here!! 

Anonymous
Not applicable

I've figured this out by learning about making an OpenAPI document describing the interface, and creating a custom connector off of the document.

  1. On the Security tab, select "API Key" for the Authentication type
  2. For "Parameter Label" put whatever you want someone to see when they are creating a Connection off of this Connector...I used "API Key"
  3. "Parameter Name" should be "Authorization" (no quotes)
  4. For "Parameter Location", select "Header"
  5. When you create a Connection off of this Connector, you'll be prompted for your "API Key" (or whatever you used for step 2 above)
  6. Enter "Bearer YOUR_BEARER_TOKEN_VALUE" (no quotes)

This will pass your bearer token to the API successfully.

Nice, I will try this. However, this doesn't work with an expiring token.

Anonymous
Not applicable

This did not work for me. Actually nothing has to this point. I've tried encoded Basic authentication with api key and bearer token but still get 401 unauthroized.

Anonymous
Not applicable

This works for me as the admin-developer. However when sharing the app with end users, it forces them to enter the API Key to use the application.

 

Is it known if there is a way to work-around this functionality?

keatklein
Regular Visitor

The solution provided by rpiwetz worked for me, sort of.  I did need to add an "accept:application/json" header to the defenition first though, otherwise I got a 401 error.

 

I said "sort of" above because I still cannot figure out a solution for an expiring token.  I can get this to work by population the connector with my expiring token, but then it only works for 1 hour.  Has anybody figured out a solution for an expiring token?

Same issue expirting token won't work with API Key. Any luck? Thank you!

I'm facing the same challenge. Have some of you found a way to do it?

I don't think it's possible if you have an expiring token.  I tried everything I could think of and never found a solution.

I found an interesting way to do this. In my case the token expires in 24 hours. So I create a seperate flow which runs every 24 hours to update the new token. Steps in the new flow

  1. Trigger to run every 24 hours
  2. HTTP request to the Authentication endpoint to generate new token
  3. Create connection action in Flow management to create a new connection for the custom connector with the token generated in the previous step
  4. Get Flow action to fetch the details of the actual flow
  5. Update Flow action to update the new connection to the flow

Now every 24 hours new connection is created and used by the flow. It works for me. But i would like to have a Edit connection action which would be more helpful. Please vote for this idea.

https://powerusers.microsoft.com/t5/Flow-Ideas/Edit-connection-in-Flow-management-connector/idi-p/35...

Hi @Dinesh, just wondering how are you updating your flow with a new connection? I tried using the Update Flow action to update the "connection reference" with the ID and Name created by the Create Connection Action. It works for the first run. But when I refresh my flow, the custom connectors result in a "connector not found" error.

 

Cheers,

Qui

Hi @Dinesh ,

 

i just followed your steps, but i dont know what i have to put in Flow Display Name and Flow Definition.

Screenshot at Oct 22 15-28-51.png

 

Thanks in advance!

Paul

I'm also unsuccessfully attempting to figure out how to get this working using all the old responses and this thread.  I have a Bearer token that expires every 15 minutes and a refresh token that expires every 24 hours.  How do I get and pass these back to my custom connector to be used by my PowerApp?  I'm able to do a Return to PowerApps to get the data back to the app but i'm having to make my flow do all the HTTP calls based on switches and variables and it's painful so i'd prefer to use a custom connector.

Hi,

 

meanwhile i found a proper solution. I realized the connection without any custom connectors. You just have to take the HTTP integration (directly in the flow) and make a POST to get the API token instantly. Create a HTTP GET step and use the token from above.

screenshot.png

 

Best

Paul

 

Brilliant @paulstegmann !  This solution worked perfectly for a custom REST API I was dealing with.  Thank you!

clh
Advocate I
Advocate I

Ugh, yes, the solution given is worthless for an expiring token.  I need to be able to pass the token as a parameter to the action, not have the token be embedded in the "connection."

 

I tried adding the Authorization header as a header in the custom connector action definition, but the custom connector editor won't let me.  It gives an error and says to use the API Key solution mentioned here, which again, won't work.

I know I can accomplish what I need with a standard Power Automate using the HTTPS connector, but that's going to take SO much more coding!

Yoshi1
Advocate I
Advocate I

In your queries, create a header named "access-token" (to put your token in)

Yoshi1_1-1661248779835.png

 

Create a policy as following and apply it to your requests ("operations" field) requiring authentication. It will replace the headers "access-token" by "Authorization"

Yoshi1_0-1661248721941.png

 

 

 

Helpful resources

Announcements

Community will be READ ONLY July 16th, 5p PDT -July 22nd

Dear Community Members,   We'd like to let you know of an upcoming change to the community platform: starting July 16th, the platform will transition to a READ ONLY mode until July 22nd.   During this period, members will not be able to Kudo, Comment, or Reply to any posts.   On July 22nd, please be on the lookout for a message sent to the email address registered on your community profile. This email is crucial as it will contain your unique code and link to register for the new platform encompassing all of the communities.   What to Expect in the New Community: A more unified experience where all products, including Power Apps, Power Automate, Copilot Studio, and Power Pages, will be accessible from one community.Community Blogs that you can syndicate and link to for automatic updates. We appreciate your understanding and cooperation during this transition. Stay tuned for the exciting new features and a seamless community experience ahead!

Summer of Solutions | Week 4 Results | Winners will be posted on July 24th

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**   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.   Community MembersNumber SolutionsSuper UsersNumber Solutions Deenuji 9 @NathanAlvares24  17 @Anil_g  7 @ManishSolanki  13 @eetuRobo  5 @David_MA  10 @VishnuReddy1997  5 @SpongYe  9JhonatanOB19932 (tie) @Nived_Nambiar  8 @maltie  2 (tie)   @PA-Noob  2 (tie)   @LukeMcG  2 (tie)   @tgut03  2 (tie)       Week 2 Results: Congratulations to the Week 2 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 2: Community MembersSolutionsSuper UsersSolutionsPower Automate  @Deenuji  12@ManishSolanki 19 @Anil_g  10 @NathanAlvares24  17 @VishnuReddy1997  6 @Expiscornovus  10 @Tjan  5 @Nived_Nambiar  10 @eetuRobo  3 @SudeepGhatakNZ 8     Week 3 Results: Congratulations to the Week 3 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 3:Community MembersSolutionsSuper UsersSolutionsPower Automate Deenuji32ManishSolanki55VishnuReddy199724NathanAlvares2444Anil_g22SudeepGhatakNZ40eetuRobo18Nived_Nambiar28Tjan8David_MA22   Week 4 Results: Congratulations to the Week 4 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 4:Community MembersSolutionsSuper UsersSolutionsPower Automate Deenuji11FLMike31Sayan11ManishSolanki16VishnuReddy199710creativeopinion14Akshansh-Sharma3SudeepGhatakNZ7claudiovc2CFernandes5 misc2Nived_Nambiar5 Usernametwice232rzaneti5 eetuRobo2   Anil_g2   SharonS2  

Check Out | 2024 Release Wave 2 Plans for Microsoft Dynamics 365 and Microsoft Power Platform

On July 16, 2024, we published the 2024 release wave 2 plans for Microsoft Dynamics 365 and Microsoft Power Platform. These plans are a compilation of the new capabilities planned to be released between October 2024 to March 2025. This release introduces a wealth of new features designed to enhance customer understanding and improve overall user experience, showcasing our dedication to driving digital transformation for our customers and partners.    The upcoming wave is centered around utilizing advanced AI and Microsoft Copilot technologies to enhance user productivity and streamline operations across diverse business applications. These enhancements include intelligent automation, AI-powered insights, and immersive user experiences that are designed to break down barriers between data, insights, and individuals. Watch a summary of the release highlights.    Discover the latest features that empower organizations to operate more efficiently and adaptively. From AI-driven sales insights and customer service enhancements to predictive analytics in supply chain management and autonomous financial processes, the new capabilities enable businesses to proactively address challenges and capitalize on opportunities.    

Updates to Transitions in the Power Platform Communities

We're embarking on a journey to enhance your experience by transitioning to a new community platform. Our team has been diligently working to create a fresh community site, leveraging the very Dynamics 365 and Power Platform tools our community advocates for.  We started this journey with transitioning Copilot Studio forums and blogs in June. The move marks the beginning of a new chapter, and we're eager for you to be a part of it. The rest of the Power Platform product sites will be moving over this summer.   Stay tuned for more updates as we get closer to the launch. We can't wait to welcome you to our new community space, designed with you in mind. Let's connect, learn, and grow together.   Here's to new beginnings and endless possibilities!   If you have any questions, observations or concerns throughout this process please go to https://aka.ms/PPCommSupport.   To stay up to date on the latest details of this migration and other important Community updates subscribe to our News and Announcements forums: Copilot Studio, Power Apps, Power Automate, Power Pages

Users online (4,101)