-
Notifications
You must be signed in to change notification settings - Fork 272
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Authentication error when executing HTTP trigger #1490
Comments
@charisk Which version of the durable-functions npm package are you using? If it's an old version, then that could explain why you're still running into this. Also, you mentioned you see this occasionally...does that mean sometimes it works fine and only sometimes it fails with a 401? Adding @davidmrdavid |
@cgillum we're using version |
@charisk okay, that's very odd. I think we'll need to look at our internal telemetry to understand where that 401 is coming from. Is there any more information you can provide us that will help us identify your function app, like a function name, the app name, or a function invocation ID? |
Thanks for looking into this @cgillum! I see an invocation ID of |
Hey @cgillum, did you have a chance to look into the issue by any chance? |
Hey @charisk. I looked at it just now, and I confirmed that it looks like your app is indeed not using the local RPC endpoint, which partly explains why you got that 401. I also confirmed that your app appears to have been using v1.8.5 of the extension. According to our release notes for v1.8.5, this should not be the case. You may want to consider upgrading to a newer version of the extension. I know we made some improvements in v1.8.6, though I'm not sure whether they would specifically help in this case. @ConnorMcMahon can you help investigate this issue (I'm currently on-call for App Service and weighed down by other issues at the moment)? |
I cannot for the life of me figure out why your app is not using the local RPC endpoint. Given your host.json and the value for In the meantime, I would try explicitly setting it to true in your host.json. You can do that by adding this to your host.json:
|
Thank you @cgillum and @ConnorMcMahon for looking into the issue for us.
We've turned We've upgraded to 1.8.6 (by executing |
@charisk, glad you were able to figure out how to install 1.8.6, installing extensions can be rather tricky for non-.NET language. As a long-term solution, I would recommend transitioning from v1 of the extension bundles to v2. We are unlikely to release many new versions of v1, just due to the maintenance cost of adding to an old branch like that, so most future bug fixes and improvements will be best gotten through v2 of the extension bundle. There are instructions for that here. There is no rush if v1.8.6 fixes your issue (which it should given the description), but for future proofing your app that would be my recommendation! |
This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment. |
We've now had the fix live for a few days and have not seen occurrences of this issue so the bug can be closed. Thanks for the help @cgillum and @ConnorMcMahon! |
Description
Occasionally, when running an HTTP trigger function, an authentication error occurs.
Expected behavior
No authentication errors happening when the HTTP trigger is executing.
Actual behavior
Every now and then, we seem to get an authentication error when executing an HTTP trigger in our function app. The HTTP trigger kicks off an orchestration. The following error is logged.
Message:
Call Stack:
The function app is using app key authentication (using the
x-functions-key
header).This might be relevant to #1348 although I believe the extension bundle version that we're running is 1.8.5 as this is what I see loaded in the KUDU process explorer (Microsoft.Azure.WebJobs.Extensions.DurableTask.dll 1.8.5)
Relevant source code snippets
N/A.
Known workarounds
N/A
App Details
Screenshots
N /A
If deployed to Azure
The text was updated successfully, but these errors were encountered: