You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+17-1Lines changed: 17 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -21,7 +21,23 @@ This projects is open source and may be redistributed under the terms of the [Ap
21
21
Adding change log starting with version 3.1.3
22
22
23
23
### 4.0.0
24
-
Information will be added soon.
24
+
Starting from 4.0.0, support for Azure Functions V4 Isolated mode with ASPNET Core integration is added.
25
+
The package is now split into two separate packages, one for each mode.
26
+
27
+
The package for Azure Functions V3+ In-Proc mode is now called `DarkLoop.Azure.Functions.Authorization.InProcess` and the package for Azure Functions V4 Isolated mode with ASPNET Core integration is called `DarkLoop.Azure.Functions.Authorize.Isolated`.
28
+
29
+
-#### .NET 6 support
30
+
Starting with version 4.0.0, the package is now targeting .NET 6.0. This means that the package is no longer compatible with .NET 5 or lower. If you are using .NET 5 or lower, you should use version 3.1.3 of the package.
31
+
32
+
-#### DarkLoop.Azure.Functions.Authorize v4.0.0
33
+
This package is published but is now deprecated in favor of `DarkLoop.Azure.Functions.Authorization.InProcess`. All it's functionality remains the same. It's just a way to keep package naming in sync.
The `IFunctionsAuthorizationProvider` interface is introduced to allow for custom authorization filter provisioning to the framework.
37
+
By default the framework relies on decorating the function or type with `[FunctionAuthorize]`. You could skip this decoration and provide the middleware with an authorization filter sourced from your own mechanism, for example a database.
38
+
At this moment this can be done only with Isolated mode even when the interface is defined in the shared package.<br/>
39
+
Support for In-Process will be added in a future version, once source generators are introduced, as the in-process framework relies on Invocation Filters to enable authorization.
40
+
Replacing the service in the application services would break the authorization for in-process mode at this point.
25
41
26
42
### 3.1.3
27
43
3.1.3 and lower versions only support Azure Functions V3 In-Proc mode. Starting from 4.0.0, support for Azure Functions V4 Isolated mode with ASPNET Core integration is added.
0 commit comments