Azure / logicapps

Azure Logic Apps labs, samples, and tools
MIT License
357 stars 299 forks source link

Where can I find the signature when executing the Logic App locally? #169

Closed mikaelsand closed 3 years ago

mikaelsand commented 3 years ago

I am able to start the Logic App. I get the address in the output window: http://localhost:7071/api/INT001/triggers/manual/invoke. Then I get asked for the version, ok I find it by faking another version, but then I get this error.

{ "error": { "code": "AuthorizationFailed", "message": "Required parameters for shared access URL are permissions ('sp'), version ('sv'), and signature ('sig')." } } If I look in the designer it says that I cannot get the URL because I am running locally. Where can I find the params I need to execute the Logic App locally?

tomkerkhove commented 3 years ago

During preview it was stored in an Azure table

tomkerkhove commented 3 years ago

See https://github.com/Azure/logicapps/issues/123#issuecomment-644137876

rarayudu commented 3 years ago

If you are running from VS Code, you can open overview of the workflow and you can find the trigger url there.

image

mikaelsand commented 3 years ago

This is my Overview: image

So I started my local environment by doing an F5: image And this is a very empty result.

mikaelsand commented 3 years ago

See #123 (comment)

Thanks. I read it and I just got dizzy from reading all that text. This should not be hard, I feel.

tomkerkhove commented 3 years ago

Jup but maybe it got easier in public preview

rohithah commented 3 years ago

can you make sure your workflow is running locally? (either F5 from VS code or do a "func start" from the project folder)?

lynnaloo commented 3 years ago

I'm getting this same "failed to fetch" error in the Overview and when I deploy, it does not deploy the workflow even though it will run locally.

rasavant-ms commented 3 years ago

Same thing.

Repro Steps: After creating workflow with HTTP trigger, click Overview option on the workflow.json file. The complete URL to be used to send in an HTTP request is not visible. image

System Info: Azure Functions Core Tools (3.0.2931 Commit hash: d552c6741a37422684f0efab41d541ebad2b2bd2) Function Runtime Version: 3.0.14492.0 Windows 10.0.19042 Build 19042 VSCode: Version: 1.50.1 (user setup) Commit: d2e414d9e4239a252d1ab117bd7067f125afd80a Date: 2020-10-13T15:06:15.712Z Electron: 9.2.1 Chrome: 83.0.4103.122 Node.js: 12.14.1 V8: 8.3.110.13-electron.0 OS: Windows_NT x64 10.0.19042

mikaelsand commented 3 years ago

Hey guys? Any progress on this. I just downloaded the latest version. I am running the Logic App and this is my design surface and overview. Where can I please find the signature for calling the Logic App Locally? Where am I supposed to find it? I can't even find that anywhere? Or am I just supposed to deploy it to Azure during this part of the preview? image image

rohithah commented 3 years ago

can you make sure you follow the below steps:

  1. Run the app (press F5) and make sure you have success logs in the terminal window (you will see errors if the workflow failed to load): image

  2. Select the workflow.json, right click and select "overview"

image

  1. 2 should open a tab and that will show you the overview with the callback url:

image

StefanPuntNL commented 3 years ago

Also don't forget to start the Storage Emulator if you have set "AzureWebJobsStorage": "UseDevelopmentStorage=true" in local.setting.json

mikaelsand commented 3 years ago

Great! Now it works! I think that I opened the Overview window while the app was not running, and after I started the function the "Refresh" did not work ... or something.

Honestly: I think do not know the exact difference, but now it works. Thank you :-)

ahmedsza commented 3 years ago

I am having the same issues and none of above works :-(