Azure / Azure/azure-functions-host

non static V2 functions throws error when using AddAuthentication() in functionstartup

Open
#4,485 14 comments 10 reactions 0 assignees View on GitHub
enhancement
Dominant language
C#
Stars
2k
Forks
482
Avg merge
2d 12h
Merged PRs (30d)
38

Description

#### Is your question related to a specific version? If so, please specify:
Azure function v2 . .net core 2.2
#### What language does your question apply to? (e.g. C#, JavaScript, Java, All)
C#
#### Question
Am trying to implement custom token authentication with auth server . So i have used builder.Services.AddAuthenticatio in the FunctionStartUp, Am able to compile it . But while running in the local with the emulator.

When i call Http trigger functions am getting following error .

An unhandled host error has occurred.
Microsoft.AspNetCore.Authentication.Core: No authentication handler is registered for the scheme 'WebJobsAuthLevel'. The registered schemes are: BearerIdentityServerAuthenticationJwt, BearerIdentityServerAuthenticationIntrospection, Bearer. Did you forget to call AddAuthentication().Add[SomeAuthHandler]("WebJobsAuthLevel",...)?.

Can some one help me on this please ???

Does azure functions support middlewares with the latest release ?

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the local HTTP-trigger invocation from FunctionStartup after calling AddAuthentication(), using the reported Azure Functions v2 and .NET Core 2.2 setup. Trace how the WebJobsAuthLevel scheme is registered versus the listed custom schemes; done requires either a confirmed fix for the missing handler or clear documentation that this middleware configuration is unsupported.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure, csharp
Domain
authentication, backend, cloud
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.