Updating user role using asp.net identity
I have the following problem. While using the following code below to change the user’s current role i am getting an exception with the message like below:
I have the following problem. While using the following code below to change the user’s current role i am getting an exception with the message like below:
The default Identity provider provided in ASP.NET 5 has very strict password rules by default, requiring a lower case character, an upper case character, a non-alphanumeric character, and a number. I am looking for a way to change the password requirements for the provider.
I need to set my login to use username instead of email address, how can I change it?
There are many samples online using OWIN/Katana to find users in a database based on ausername/password combination and generate a claims principal, such as…
I changed the primary key for the user database from string to int using the tutorial here, but I’m having difficulty initializing the Role Manager. It used to be initialized using
I am using ASP.NET MVC identity and when I add an email of the form [email protected] I get the validation error message
I’m trying to find a way to disable a user in Identity 2.0 and can’t seem to find any info on it.
In Move ASP.NET Identity store to EF Sql database zoidbergi described an issue similar to that which I’m experiencing, but which was not completely answered. I am receiving the error above when attempting to migrate from the inbuilt .mdf database to MySQL. I am using a Database-First methodology and have successfully created the Entity Model from the underlying Mysql database.
I have installed the nightly build of the AspNet-identity assemblies from here
What is the difference between using AuthenticationManager SignIn as opposed to using SignInManager PasswordSignIn/SignIn? I have an implementation using the SignInManager and have my cookie expiration set to 30 days however it seems my web app will randomly expire my cookies far before 30 days. Would using the SignInManager implementation be the cause of this? Should I be using the AuthenticationManager implementation instead?