The problem(s) with Azure Functions

Cloud Computing Identity And Access Management Cloud Hosting

Microsoft Azure Functions Landing Page

1

Microsoft Azure Functions

Serverless, also known as FaaS (Function-as-a-Service), is a new approach to application development. FaaS is a form of serverless computing with an infrastructure managed by the provider to upload functions and use them on a pay-per-request basis.

Before that, I spend a ton of time testing Azure Functions and stumbled over a few rocks mountains 🗻.

#Cloud Hosting #Cloud Computing #Developer Tools 19 social mentions
Auth0 Landing Page
2

Auth0

Auth0 is a program for people to get authentication and authorization services for their own business use.
Pricing:
- Open Source
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.

#Identity And Access Management #Identity Provider #SSO 175 social mentions