Trigger Logic app using web activity | Failing because of authorization

[muja_86]

I have logic app with HTTP post request which will transfer some file from sharepoint site to adls gen2. Its working via postman request but when i am trying to send request via web activity, there i have created connection with anonymous authorization and even tried providing basic credentials but its failing at authorization.

[v-csrikanth]

Hi @muja_86 

We haven't heard from you since last response and just wanted to check whether the solution provided has worked for you. If yes, please Accept as Solution to help others benefit in the community.

If the above information is helpful, please give us Kudos and mark the response as Accepted as solution.
Best Regards,
Community Support Team _ C Srikanth.

[v-csrikanth]

Hi @muja_86 
It's been a while since I heard back from you and I wanted to follow up. Have you had a chance to try the solutions that have been offered?
If the issue has been resolved, can you mark the post as resolved? If you're still experiencing challenges, please feel free to let us know and we'll be happy to continue to help!
Looking forward to your reply!

Best Regards,
Cheri Srikanth

[v-csrikanth]

Hi @muja_86 

Thank you for being part of the Microsoft Fabric Community.

As highlighted by @nilendraFabric , the proposed approach appears to effectively address your requirements. Could you please confirm if your issue has been resolved?
If you are still facing any challenges, kindly provide further details, and we will be happy to assist you.

Best Regards,
Cheri Srikanth

[nilendraFabric · Accepted solution]

Hi @muja_86 

The error "DirectApiRequestHasMoreThanOneAuthorization" occurs when your request to a Logic App contains multiple authentication schemes simultaneously. This typically happens when you're trying to use both a SAS token (which is included in the Logic App URL) and another authorization method in the same request

Your Logic App URL might already contains a SAS token (in the format https://<request-endpoint-URI>?sp=<permissions>&sv=<SAS-version>&sig=<signature>), but you're also sending an Authorization header in your web activity

• In your Web Activity, use "Anonymous" authentication

• Don't add any Authorization headers

• Keep the full URL with the SAS token intact