search

aspnet / Tooling

Issue tracker and info on Visual Studio tooling for ASP.NET
Other
258 stars 124 forks source link

Why user individual account option is disabled on asp.net core web api and VS2017 RC4? #1005

Closed MaherJendoubi closed 7 years ago

MaherJendoubi commented 7 years ago

image

mlorbetske commented 7 years ago

Hi @MaherJendoubi, this hasn't been enabled as there'd be some odd experiences around it with the way this works today (there'd have to be a signup experience or the backing database would have to come from another project, etc.). We've been talking through what this should look like for a while & have an idea of what this will look like and have a plan to do something similar in an upcoming release of Visual Studio 2017.

MaherJendoubi commented 7 years ago

@mlorbetske Have you an idea if it will be fixed in the RTM release next week?

mlorbetske commented 7 years ago

@MaherJendoubi this won't be in the RTM release, but in an update that follows

MaherJendoubi commented 7 years ago

@mlorbetske Thank you for the reply!

Daedalus72 commented 7 years ago

What about this issue, 3 months have been passed and no answer at all... If someone wants to build a .net core web api site with facebook auth, how can achieve it without being given the tools?

mlorbetske commented 7 years ago

@vgpallis for .NET Core 2.0 (or higher) individual auth for WebAPI is planned. My understanding is that @blowdart has the details on when we'd be planning to add support for more auth pivots for Web API.

blowdart commented 7 years ago

If by individual auth you mean there's the ability to have an auth server, which issues bearer tokens, which can be use in authenticating and authorizing an api endpoint it'll be 2.1.

But for facebook, it's just oauth, so acquiring the token is up to you (and facebook has SDKs), and validating it is calling facebook endpoints.