[Feature Request] New template for .NET 6.0 Azure functions
See original GitHub issueIs your feature request related to a problem? Please describe. Microsoft.Identity.Web supports NET Core 3.1 Azure functions, but there is now a new model
Describe the solution you’d like Provide a project template for .NET 5.0 Azure functions
Additional context
func new --name SampleFunc --template "HTTP trigger" --authlevel "anonymous"
Issue Analytics
- State:
- Created 2 years ago
- Reactions:3
- Comments:6 (3 by maintainers)
Top Results From Across the Web
.NET 6.0 in Azure Functions is now generally available | ...
Azure Functions support for .NET 6.0 is now generally available in Azure Functions runtime 4.0. .NET 6.0 is the latest Long Term Support ......
Read more >Guide for running C# Azure Functions in an isolated worker ...
This article is an introduction to working with .NET Functions isolated worker process, which runs your functions in an isolated worker ...
Read more >DiagnosticSource in Azure Function .Net 6.0
The new DiagnosticSource event Microsoft.AspNetCore.Server.Kestrel.BadRequest now contains a IBadRequestExceptionFeature that can be used to ...
Read more >Create your first C# function in Azure using Visual Studio
The Azure Functions project template in Visual Studio creates a C# class library project that you can publish to a function app in...
Read more >Quickstart: Add feature flags to an Azure Functions app
In this quickstart, use Azure Functions with feature flags from Azure App Configuration and test the function locally.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
While this is not directly related to Microsoft.Identity.Web, I did a sample on the out-of-process model with token validation (thanks @damienbod for the head start!) and calls to Microsoft Graph and token exchange via MSAL.
Blog post: https://hajekj.net/2022/04/22/azure-functions-out-of-process-and-authentication-with-azure-ad/ Sample code: https://github.com/hajekj/azure-functions-dotnet-worker-miw
@hajekj @MarcAnnous I extended the solution from Christos Matskas and Boris Wilhelms and added some extra validation which should not be skipped and can be used with any DI and returns the claims.
https://damienbod.com/2020/09/24/securing-azure-functions-using-azure-ad-jwt-bearer-token-authentication-for-user-access-tokens/
I think JWT Bearer auth should be out-of-the-box for any Identity provider using oauth in Azure Functions. Not “just” AAD should be supported although I like this really a lot.
There are also other JWT auth github projects to fulfil this gap.
Greetings Damien