I have already tried to use out of box of ASP.NET membership provider and MembershipReboot.
but I also would like to know is there any way that I can integrate ASP.NET Identity V2?
You can use the same extensibility points that both Membership and MembershipReboot use to support ASP.NET Identity.
Related
I know how to add external provider using .net Core Identity for Google, But i couldn't get any example to implement for Azure AD SSO using SAML2.So far i know we can use Sustainsys library to configure SAML2.
Exising code :
var result = await _signInManager.PasswordSignInAsync(Input.Email, Input.Password, Input.RememberMe, lockoutOnFailure: true);
if (result.Succeeded)
{
//Redirect to Login page
}
I have tried using Sustainsys library to implement , But there is no sample code or documentationusing ASP.NET identity.
While the Sustainsys.Saml2 library can certainly be used with Azure AD, I'd recommend using the OpenID Connect packages from Microsoft that are built for Azure AD. They provide a better experience.
We need to build a Grpc service, which must feature users, external login, sign-in/sign-out, roles, etc. We plan to use EF Core for our database, so we consider using ASP.NET Core Identity for all that "user stuff".
Will Grpc work nicely with ASP.NET Core Identity? I just found out that Microsoft suggests not to use their Identity framework for web APIs (mentioned here: https://learn.microsoft.com/en-us/aspnet/core/security/authentication/identity). So did I misunderstand them, or are there pitfalls in that approach?
I Created application using asp.net core with mysql database.
Right now, I need to implement authentication and i want to use Asp.net idenity.
But i not able to found any proper integration of asp.net identity with mysql database.
I was able to use MySQL with Identity in this project : https://github.com/aguacongas/chatle
Read Startup.cs on branche release/1.1.1 if you want a sample with .Net Core 1.1
Use the dev branch for .Net 2.0
I want to compare authentication methods in asp.identity and dotnetnuke. I have read very articles about authentication in dotnetnuke.
DNN AUTHENTICATION WITH NEW ASP.NET IDENTITY SYSTEM
DotNetNuke Tips and Tricks #12: Creating your own Authentication Provider
Using DNN authentication and authorization info from another ASP.NET app
How to Setup the Authentication Settings in DotNetNuke
But I din't understand authentication elements and the relationship between them.
It would be very helpful if someone could explain authentication method in dotnetnuke.
Thanks.
DotNetNuke uses Asp.Net Membership not Identity. To replace the core authentication provider would be a lot of effort.
There are several ways to create your own authentication provider, but ultimately it will still be using the DotNetNuke Asp.Net Membership process. If you want to use an external service that uses Asp.Net Identity you could have your external Asp.Net Identity service pass a token/cookie to a custom DotNetNuke authentication/redirect module that validates the token/cookie, migrates the user from the Asp.Net Identity database to the DotNetNuke Asp.Net Membership database and finally does the login: DotNetNuke.Entities.Users.UserController.UserLogin.
Why it`s not possible to create Web API project with Individual User Accounts Authorization type?
UPDATE:
All version numbers are updated from v1.2 to v2.0.
Please find the ASP.NET Core Schedule and Roadmap:
Identity Application Services
A service layer will be added ASP.NET Core Identity and included in the project templates using Individual Authentication. This will allow authentication of users by way of JWT tokens such that Web APIs can be secured out of the box, and make it simpler to change authentication systems, e.g. from in-app Identity to Azure AD B2C, or 3rd-party solutions like Identity Server.
Daniel Roth from MS:
Support for individual user accounts with the Web API template in VS is not available yet. We are still looking at providing a supported on premise offering for token issuance in addition to providing integration with Azure AD B2C.
This statement can be found in the comment section under https://channel9.msdn.com/Events/dotnetConf/2016/Building-Secure-Web-APIs-with-ASPNET-Core
This is just disabled in core 1.1.please use core 2.0 to find all authentication.You can download core 2.0 from
here