cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
bharatmalviya
New Member

Optional password in HTTP connector Basic Authentication

Dear Team,

I have created a Power Automate workflow that contains HTTP Action. This action calls external REST API with "Basic" Authentication type. The API service provide expects only username and not password for calling the service.

 

However, HTTP action has password mandatory with Basic authentication thus the flow is not executing the connector with below error:

The required basic authentication property 'password' is missing.

Below is the screenshot of HTTP action designer:

 

bharatmalviya_0-1595386500557.png

 

Below is screenshot of exception

bharatmalviya_2-1595385891498.png

 

The  API provider is one of the leading bank in Australia where the payment file to be uploaded. Below is the documentation of API provider:

 

https://paymentsplus-wbc.support.qvalent.com/docs/wbc/paymentsplusapi/v1/#credentials-and-security

 

When the username is provided in Password field, the API throws an exception that they are not expecting password. 

 

Can someone please advise if there is a way to suppress the password during API call? Appreciate the help. 

 

Thanks.

6 REPLIES 6
Anonymous
Not applicable

 

 

It seems that you cannot leave the password empty.

Hi @Anonymous ,

 

Thanks for the response. We tried same thing in Logic Apps however Power Automate internally uses HTTP Logic App connector.

 

I'm looking for another approach where we may need to invoke REST API using Windows service. As the API provider expect the calls from specific IP range only. 

Hi @bharatmalviya 

 

I had the similar issue where I need to use the username as my API key and no password. I used the below config. Use the HTTP connector and set the Authentication as Raw. Under the Value place the API key.

 

image.png



Did I answer your question? Mark my post as a solution!

If you liked my response, please consider giving it a thumbs up


Proud to be a Flownaut!

Learn more from my blog
Power Automate Video Tutorials

Hi @abm ,

 

Thanks, I'll have a look into and check whether it works. 

 

 

Anonymous
Not applicable

To resolve the authentication issue. Copy the username in the password field.

bemadmonkey
New Member

In my case, the endpoint required authentication header in the following format:

Authorization: Basic <base64("username:password")>

where username is the API key and password blank. 

 

I solved it using the "Raw" option and set its value to "Basic base64('username:')"

Screenshot 2022-05-19 at 13.46.20.png

In the screenshot above, the value after "Basic" is a calculated base64 representation of the string "username:". The username is the API key. Note the colon ":" after "username". That is required (at least in my case).

 

Optionally, base64() is available as an expression when using the dynamic content option. One can use that as well, especially if you want to keep the username secret. 

 

Helpful resources

Announcements
Power Platform Conf 2022 768x460.jpg

Join us for Microsoft Power Platform Conference

The first Microsoft-sponsored Power Platform Conference is coming in September. 100+ speakers, 150+ sessions, and what's new and next for Power Platform.

New Ideas Forum MPA.jpg

A new place to submit your Ideas for Power Automate

Announcing a new way to share your feedback with the Power Automate Team.

MPA Virtual Workshop Carousel 768x460.png

Register for a Free Workshop

Learn to digitize and optimize business processes and connect all your applications to share data in real time.

MPA Licensing.jpg

Ask your licensing questions at the Power Automate AMA!

Join Priya Kodukula and the licensing team, super users and MVPs to find answers to your questions on Power Automate licensing.

Users online (2,491)