So here’s how the MySql membership works (as I recall):

There’s an initialize method that is called anytime a Membership implementation is enabled and starts up. During initialize, it always checks the schema version. If autogenerateschema is set to “true” and the schema version doesn’t exist or needs to be updated, it will automatically apply any incremental (or full) updates to the database schema at that time. The caveat here is that your application credentials used by your membership data connection also require schema change access to the database.

If the data connection does not have proper access to change schema or if the schema version in the current database needs to be updated but autogenerateschema is false, then you will see exceptions thrown.

In a happy scenario, MySql Membership provider will automatically update your schema as needed and just plain work when you try to use it.

Good luck!

I have downloaded Community edition of Mysql from http://www.mysql.com using windows installer. ASP.NET Membership generates bunch of Stored procedures automatically. Now we know that the syntax differs for MS Sql Server and MySql, by mentioning “autogenerateschema=true”, does the provider manages the schema for MySql? or its ASP.NET configuration tool that does that?

I do have one question. When using the ASP.Net Web Site Administration Tool is it normal that if you try and test the Providers on the Provider tab the test fails? Everything on with my membership appears to be working properly I just wanted to make sure there wasn’t something behind the scene that might not and cause me problems down the road.

Thanks!!

One of the things built-in to the MySql connector’s membership provider is the ability to migrate schema for you. If you enable it with the attribute option, “autogenerateschema=true”. Set this on each of the membership section: membership, profile, and roles. Make sure the connection string you configured is using a mysql user account with full privileges to the database. Most hosting providers only give you one, so that shouldn’t be a problem. The tool above has an option to generate a configuration with autogenerate schema enabled if you want to see what it looks like in action.

Hope that helps!

You bet! What error are you getting?

Take a look at my most recent post w/ Mono 2.8 and MySql Membership. I haven’t tested encryption specifically, but I did make it work with hashed passwords. I’ll look into it an get you a better answer if that’s still an issue.