asp.net-identity

Closed . This question needs to be more focused. It is not currently accepting answers. Learn more . Want to improve this question? Update the question so it focuses on one problem only by editing this post . Closed 3 years ago . In my solution folder there are two projects Myproject.API Myproject.Web API will server all the request to My Mvc web or android or IOS client. Now Here I'm confused, Where should I Implement Authentication process. At API or At API and MVC both As MVC identity uses Cookie based authentication where as API used token based. Now What I want In Web Project, If any user

When registering an account through Web API with an email such as "xxx-yyy@gmail.com", Fiddler returns the follow error. Note that email is used for username as well, so both fields are the same . But it works when registering on MVC itself. ExceptionMessage=User Creation Failed - Identity Exception. Errors were: User name xx-yyy@gmail.com is invalid, can only contain letters or digits. User Object var newUser = new ApplicationUser { UserName = user.Email, Email = user.Email }; IdentifyConfig.cs public static ApplicationUserManager Create(IdentityFactoryOptions<ApplicationUserManager> options,

Are there any major advantages of using OWIN cookie-based authentication over Forms Authentication cookie-based authentication for developing MVC web applications? The reason I ask is that I would not be using any of the Entity Framework based hooks for OWIN authentication. I've built apps based on Forms Authentication for years and have been able to do things like create different authentication tokens for admins (faster timeouts), anonymous users, and registered users. Using the UserData portion of the ticket I was able to implement universal sign out, store custom properties, etc. One of

Our application doesn't need the excessive "Logins" and "Claims" functionality that identity uses. It would be nice if these tables simlpy didn't get created in the database, but I don't want to have to reimplement all identity classes... I'd assume it's something like public ApplicationDbContext : IdentityDbContext { [...] protected override void OnModelCreating(DbModelBuilder modelBuilder) { base.OnModelCreating(modelBuilder); modelBuilder.Ignore<IdentityUserClaim>(); modelBuilder.Ignore<IdentityUserLogin>(); } } You would think this works according to the function descriptions, but it doesn

Using MVC Core with ASP.NET Identity I would like to change the defaults error messages of ValidationSummary that arrived from Register action. Any advice will be much appreciated. adem caglin You should override methods of IdentityErrorDescriber to change identity error messages. public class YourIdentityErrorDescriber : IdentityErrorDescriber { public override IdentityError PasswordRequiresUpper() { return new IdentityError { Code = nameof(PasswordRequiresUpper), Description = "<your error message>" }; } //... other methods } In Startup.cs set IdentityErrorDescriber public void

I have implemented ASP.Net Identity after following the sample code here: https://github.com/rustd/AspnetIdentitySample In my implementation I check if a user is authenticated - this is called from a FilterAttribute on my MVC Controllers; the idea is i want to confirm they are still auth'ed before serving up the page. So in my filter, the following code eventually gets called: _authenticationManager.User.Identity.IsAuthenticated; _authenticationManager is here: private IAuthenticationManager _authenticationManager { get { return _httpContext.GetOwinContext().Authentication; } } The

I am facing this issue with my asp.net MVC5 web application, using Identity v2.0.0.0, EF 6, Castle Windsor IOC Container, Microsoft SQL Server 2005 I am trying to get the current logged in User by using UserManagerExtensions,FindById() method but it is throwing an error "System.NotSupportedException : A second operation started on this context before a previous asynchronous operation completed. Use 'await' to ensure that any asynchronous operations have completed before calling another method on this context. Any instance members are not guaranteed to be thread safe" What I understood from the