AspNetCore.Docs VS openiddict-core

Certain parts of Microsoft Learn are permissive, for example the .NET BCL documentation is Creative Commons Attribution: https://github.com/dotnet/dotnet-api-docs as is ASP.NET Core: https://github.com/dotnet/AspNetCore.Docs (a good hint if documentation is permissively licensed and on GitHub is if there's an edit button at the top.)

The C# language specification is unfortunately a bit fuzzier: https://github.com/dotnet/csharplang/discussions/4855

The updated unified C# language specification is CC, but it's still catching up to modern C#: https://github.com/dotnet/csharpstandard

looks like 8.0 release? https://github.com/dotnet/AspNetCore.Docs/commit/e8ce5761969...

I am coming from .Net Framework and supporting the legacy apps to .Net Core ecosystem fairly recently, so I might have missed couple of release notes so please bear with me. In the .Net Framework usage of HttpContext outside HttpRequest was discouraged because it isn't thread safe. Now I get this feedback and then I google around a bit and I find topics like this: https://github.com/dotnet/AspNetCore.Docs/issues/18419 or like this onehttps://learn.microsoft.com/en-us/answers/questions/1143595/asp-net-core-web-api-how-to-use-user-claims-in-ser

I am not sure what you mean,but here you can find all the supported ways of accessing the httpcontext in.net core https://github.com/dotnet/AspNetCore.Docs/blob/main/aspnetcore/fundamentals/http-context.md maybe this can help you

Whilst EF6.3 had some support (note: designer doesn’t work) in .NET Core 3.1 (sample), I’m not sure if that applies to NET6. You could certainly give it a try.

11. ASP.NET

Also this discussion https://github.com/dotnet/AspNetCore.Docs/issues/26250

You can use Openidict https://documentation.openiddict.com/, give it a try

Openiddict to create your own OpenID Connect server if you want to deep dive into auth https://github.com/openiddict/openiddict-core

If you do want a .NET IdP then you could look into OpenIddict but will require some hands on work, at a minimum authorisation controllers. If you're looking for something more out of the box OrchardCore's OpenId module might be better for you.

Also, the OAuth bit is very cool!! Do you plan to support OpenIddict it’s a free federated identity server.

That's for Identity Server 5 (Duende) Identity Server 4 is still free, the downside though is it's not supported anymore so there's no new updates coming. For alternatives look at openiddict for something close to IS4, or host something like Keycloak on docker and talk to it via it's APIs just like how you'd do it when talking to 3rd party Auth providers.

Para la implementación de OpenID Connect en .NET utilizaremos OpenIddict-core y .NET 6.

Short answer: IdentityServer is no longer FOSS, so if that's critical, consider using https://github.com/openiddict/openiddict-core. Not as turn-key, but you'll see in their readme that OrchardCore has a bit more bells-and-whistles implementation that might appeal. Both projects are also FOSS with standard open-source licenses.

OpenIddict