Releases: dark-loop/functions-authorize
v3.1.3-preview-240211-5
Support for disabling FunctionAuthorize effect at the application level
Adding support for disabling the effect of [FunctionAuthorize] attribute at the application level.
This is useful when wanting to disable authorization for a specific environment, such as local development.
v3.1.3-preview-240211-2
Remove Functions bult-in JwtBearer configuration by default (Breaking change?)
Azure Functions recently added configuration for issuer and audience validation for the default authentication flows, not the one supported by this package through FunctionAuthorizeAttribute, which interferes with token validation when using our own Bearer scheme token configuration.
In prior versions, this package has functionality to clear Functions built-in configuration, but it was not enabled by default when using AddJwtBearer(Action<JwtBearerOptions> configure, bool removeBuiltInConfig = false). Since the use of this package is commonly used for custom JWT token, the default value of removeBuiltInConfig is now true.
v3.1.2
v3.1.2-preview-221118-1
Bug fixes
- Exception when writing to response after being started. Now there are checks before writing and correct exception is thrown.
v3.1.1
v3.1.1-preview-221107-1
Adding sample project for Azure Functions V4 and readying for release version
v3.1.1-preview-220811-1
Adding FunctionAuthorizationException for better logging handling when handling Unauthorized or Forbidden access failures.
v3.1.0
3.1.0 preview 211123-1
Merge pull request #6 from dark-loop/security Adding built-in auth to extension methods to address #5. This should enable setting up authentication at startup and not breaking access to functions in Azure portal as described in https://github.com/Azure/azure-functions-host/issues/6959