https://github.com/dark-loop/functions-authorize

An ASP.NET Core based authentication and authorization middleware for HTTP triggered Azure Functions (In-Proc and Isolated)
https://github.com/dark-loop/functions-authorize

authentication authorization authorize-attribute authorizeattribute azure azure-functions azure-functions-v3 azure-functions-v4 isolated policy-based-authentication policy-based-authorization

Last synced: 5 days ago
JSON representation

An ASP.NET Core based authentication and authorization middleware for HTTP triggered Azure Functions (In-Proc and Isolated)

• Host: GitHub
• URL: https://github.com/dark-loop/functions-authorize
• Owner: dark-loop
• License: apache-2.0
• Created: 2021-04-07T13:04:38.000Z (almost 5 years ago)
• Default Branch: master
• Last Pushed: 2025-10-23T22:44:41.000Z (3 months ago)
• Last Synced: 2025-11-27T09:36:31.246Z (about 2 months ago)
• Topics: authentication, authorization, authorize-attribute, authorizeattribute, azure, azure-functions, azure-functions-v3, azure-functions-v4, isolated, policy-based-authentication, policy-based-authorization
• Language: C#
• Homepage:
• Size: 214 KB
• Stars: 50
• Watchers: 4
• Forks: 10
• Open Issues: 11
• Metadata Files:
  • Readme: README.md
  • Changelog: ChangeLog.md
  • License: LICENSE

Awesome Lists containing this project

README

          
# functions-authorize

Extension bringing AuthorizeAttribute Behavior to Azure Functions In-Proc and Isolated mode. For the latter is only available with ASPNET Core integration.

It hooks into .NET Core dependency injection container to enable authentication and authorization in the same way  ASP.NET Core does.

> **Breaking for current package consumers** 


> Starting with version 4.1.0, due to security changes made on the Functions runtime, the Bearer scheme is no longer supported for your app functions.


> Use `AddJwtFunctionsBearer(Action)` instead of `AddJwtBearer(Action)` when setting up authentication.

Using `AddJwtBearer` will generate a compilation error when used against `FunctionsAuthenticationBuilder`. 

We are introducing `JwtFunctionsBearerDefaults` to refer to the suggested new custom scheme name.


No changes should be required if already using a custom scheme name.


> Refer to respective README documentation for isolated and in-process for more information.

## Getting Started

- [Azure Functions V3+ In-Proc mode](./src/in-proc/README.md)

- [Azure Functions V4 Isolated mode with ASPNET Core integration](./src/isolated/README.md)

## License

This projects is open source and may be redistributed under the terms of the [Apache 2.0](http://opensource.org/licenses/Apache-2.0) license.

## Package Status

### Releases

[![Nuget](https://img.shields.io/nuget/v/DarkLoop.Azure.Functions.Authorization.Abstractions.svg)](https://www.nuget.org/packages/DarkLoop.Azure.Functions.Authorization.Abstractions)

### Builds

![master build status](https://dev.azure.com/darkloop/DarkLoop%20Core%20Library/_apis/build/status/Open%20Source/Functions%20Authorize%20-%20Pack?branchName=master)

## Change Log

You can access the change log [here](https://github.com/dark-loop/functions-authorize/blob/master/ChangeLog.md).