On this line i am getting an exception -
OAuthWebSecurity.CreateOrUpdateAccount(provider, providerUserId, model.UserName);
System.Web.Security.MembershipCreateUserException: The username supplied is invalid.
The data going into this is
The initialization works fine using
WebSecurity.InitializeDatabaseConnection("club", "User", "UserID", "UserName", autoCreateTables: true);
I cannot find any examples of why it says the username is invalid? Is there a criteria somewhere that defines what is a correct user name?
I was similarly looking for an explanation to this. I'm not sure I fully understand, but after experimentation, debugging, and watching intellitrace events, it seems CreateOrUpdateAccount is creating or updating an entry in the OAuthMembership table with just Provider, ProviderUserId, and UserId which is determined by querying [in my case] the UserProfile table based on this unique UserName. This way, if you call CreateOrUpdateAccount with a different provider and providerUserId, but the same username, then both provider sign ins are tied to the same user account in your app.
I had to add a UserProfile before I could create/update the corresponding OAuthMembership record. In the VS template, it looked something like this:
db.UserProfiles.Add(new UserProfile { UserName = model.UserName });
db.SaveChanges();
OAuthWebSecurity.CreateOrUpdateAccount(provider, providerUserId, model.UserName);
I had the same problem. I solved it by specifying the correct connection string in SimpleMembershipInitializer and UsersContext class. I'm using ASP.NET MVC4
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With