Our great sponsors
-
Functions can be triggered in multiple ways: HTTP, Queue, Db, Blob Storage Change and many more. More on this can be found here. This was one of the major reasons why I thought Azure Functions are great. I mostly needed the HTTP and Queue trigger. With HTTP functions comes also the requirement for Authentication and Authorization. I'm using Auth0 as an authentication provider. The implementation is usually straightforward. The frontend obtains an access token and the API validates the token and authenticates the request. OpenID connect is well documented and somewhat easy to use in asp.net core for example. Not with Azure Functions I googled for days, opened an issue and tried everything I could think of and came to the conclusion: Microsoft doesn’t provide you with proper SDKs to handle authentication adequately.
-
AzureFunctions.Extensions.OpenIDConnect
OIDC / JWT Bearer Tokens authentication made easy for Azure Functions. Work with the well known ASPNET Authorize attribute. Compatible with popular identity providers including Auth0, Azure AD B2C, Azure AD, Google etc..
There are some libraries that workaround this problem BUT they are not well maintained and potentially use preview code that might never make it to the new Out Of Process runtime.
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
Functions can be triggered in multiple ways: HTTP, Queue, Db, Blob Storage Change and many more. More on this can be found here. This was one of the major reasons why I thought Azure Functions are great. I mostly needed the HTTP and Queue trigger. With HTTP functions comes also the requirement for Authentication and Authorization. I'm using Auth0 as an authentication provider. The implementation is usually straightforward. The frontend obtains an access token and the API validates the token and authenticates the request. OpenID connect is well documented and somewhat easy to use in asp.net core for example. Not with Azure Functions I googled for days, opened an issue and tried everything I could think of and came to the conclusion: Microsoft doesn’t provide you with proper SDKs to handle authentication adequately.
Related posts
- Default function key changes every month
- Serilog in ASP.NET Core 7.0 – Structured Logging using Serilog in ASP.NET Core 7.0
- Monitoring App Service certificate expiration dates using Azure Functions
- Discovering Azure's unannounced breaking change with Cosmos DB
- C# : System.OperationCanceledException: The operation was canceled