MySQL Bugs: #61108: Unable to login using asp:Login control connected to the membership provider

Bug #61108	Unable to login using asp:Login control connected to the membership provider
Submitted:	9 May 2011 23:36	Modified:	5 Jul 2011 6:24
Reporter:	Ben Smith	Email Updates:
Status:	Closed	Impact on me:	None
Category:	Connector / NET	Severity:	S2 (Serious)
Version:	6.3.6	OS:	Linux (Ubuntu 11.04)
Assigned to:	Julio Casal	CPU Architecture:	Any
Tags:	membership, Mono, ubuntu

Description:
I've got the most basic website with a login.aspx and a default.aspx setup with membership enabled in the web.config and forms authentication. I've added a user through the visual studio ASP.NET site configuration. When i deploy to Ubuntu i put in MySql.Data.dll and MySql.Web.dll into the bin subfolder. When i login it always comes back with "Your login attempt was not successful. Please try again." The password format is Clear.

How to repeat:
1. Create a basic website in visual studio 2008.
2. Create a login.aspx page.
3. Add a login control to login.aspx page.
4. Go through the mysql membership wizard in visual studio to add details to web.config.
5. Deploy to Ubuntu / Mono.
6. Try to login using same password as used locally on visual studio membership admin and when running the site locally through visual studio.

Have you set the applicationName attribute on your provider?

http://weblogs.asp.net/scottgu/archive/2006/04/22/Always-set-the-_2200_applicationName_220...

Yes there is an application specified.

It seems i can use the CreateUser asp.net control to create a user and then login with that users details.

What i can't do is Create a user locally, export the database using MySQL Workbench. Reimport the database remotly and login using same details.

Wierdly when i import the database and use the CreateUser asp.net control to create a new user. It looks like the schema is rewritten as all the users i added locally are zerod and the new user i added remotly has an id of 1.

Can you advise on how to do this process as it's not going to be very easy to backup users if we can move them from one machine to another.

Thanks,
Tim.

Ben,

Thank you for your interest in MySQL software.
Officially MySQL Connector/NET does not fully support MONO because it is not 100% compatible with Microsoft NET Framework.

Have you tried connecting to the same MySQL Server instance, which worked with ASP.NET from Ubuntu?

I will ask our NET developers if they can advise something to help with the problem.

Ok i've got it all working. 

One thing i would say to the connector developers is why have they named the tables with an upper case letter on the last word. What this stops you doing is creating a database on windows and exporting it and loading it into a linux database as on windows it ignores the case and uses the lower case so when you export onto linux the connector can't find the tables. Doh! Yes i realise i can mess with the upper case lower case settings but why bother.

So to get the mmebership working with hashed, salted passwords i've commeted out these two lines.

//if (Runtime.IsMono)
                //    throw new ProviderException(Resources.MonoDoesNotSupportHash);

I have the web and data projects building in my workspace on both platforms i've got ubuntu running in vmware with subversion so it's not an issue to build and deploy from this staging server. I'm using SHA1 and i specify this in the web.config and it's all working great. I have to design the database in ubuntu and export back to windows but apart from that it's the only limitation and this is due to the issue mentioned previously.

Cheers,
Ben.

Tim,

Thanks for your observations.
The developers will change the script to always create the tables in lowercase and make sure the case matches on Windows and Linux.

Thank you for your bug report. This issue has been committed to our source repository of that product and will be incorporated into the next release.

Fixed in 6.1.7, 6.2.6, 6.3.8 and 6.4.4+.

If necessary, you can access the source repository and build the latest available version, including the bug fix. More information about accessing the source trees is available at

    http://dev.mysql.com/doc/en/installing-source.html

How will this change affect existing databases whose clients are upgrading the connectors?