Did you figure it out? I am having the exact same problem. Only difference is that I am using Razor instead of Forms.
EDIT: My problem was that when setting the forms authentication cookie, I was using a different username than the one umbraco was using (the different username came from the other database). Had nothing to do with umbraco, just the fact that authentication ticket won't work if you use it with the wrong username, which makes sense.
I'm digging up an old thread here, but this may be useful to others.
It seems you are overriding the Members membership provider (frontend users) in stead of the Users membership provider (Umbraco users). It works for me if I use the Users membership provider. My solution is in Umbraco 7, so it looks like this:
custom membership provider - umbraco 6.1.6
Trying to implement a custom membership provider but its not working.
Followed http://abrissirba.wordpress.com/2012/12/02/membership-provider-in-umbraco/
Made class MyCustomMembership.cs
Created a template with a standard login control
Registred the provider in web.config
When i debug my class in VS i get true and redirected to home.aspx but are presented the login form again?
What steps am i missing?
When i switch to the default membership provider and login with my dummy user it works fine
Did you figure it out? I am having the exact same problem. Only difference is that I am using Razor instead of Forms.
EDIT: My problem was that when setting the forms authentication cookie, I was using a different username than the one umbraco was using (the different username came from the other database). Had nothing to do with umbraco, just the fact that authentication ticket won't work if you use it with the wrong username, which makes sense.
I'm digging up an old thread here, but this may be useful to others.
It seems you are overriding the Members membership provider (frontend users) in stead of the Users membership provider (Umbraco users). It works for me if I use the Users membership provider. My solution is in Umbraco 7, so it looks like this:
is working on a reply...