Membership not login me in
-
- Devart Team
- Posts: 1710
- Joined: Thu 03 Dec 2009 10:48
Fastc, please try this code:
with the setting you have mentioned when registering our provider:
isValid is true with the 5.70.124 version of dotConnect for MySQL in our test environment. Please tell us your version and your result.
We plan to release the new build in a week.
Code: Select all
MembershipCreateStatus status;
Membership.CreateUser("user", "pass!word", "[email protected]", "why?", "because", true, out status);
// status=Success
bool isValid = Membership.ValidateUser("user", "pass!word");
// isValid=true
Code: Select all
...
We plan to release the new build in a week.
Having same issue
I am trying your solution but I get this in returnShalex wrote:Fastc, please try this code:with the setting you have mentioned when registering our provider:Code: Select all
MembershipCreateStatus status; Membership.CreateUser("user", "pass!word", "[email protected]", "why?", "because", true, out status); // status=Success bool isValid = Membership.ValidateUser("user", "pass!word"); // isValid=true
isValid is true with the 5.70.124 version of dotConnect for MySQL in our test environment. Please tell us your version and your result.Code: Select all
...
We plan to release the new build in a week.
5.70.124.0 is version.Unrecognized attribute:hashAlgorithmType
Do I need to reference an additional assembly?
dotConnect for MySQL v 5.80 is released!
It can be downloaded from http://www.devart.com/dotconnect/mysql/download.html (trial version) or from Registered Users' Area (for users with valid subscription only).
For more information, please refer to http://www.devart.com/forums/viewtopic.php?t=18031 .
KW, please try this latest build. It seems like that the Unrecognized attribute:hashAlgorithmType error you have got when making a workaround was caused by setting the hashAlgorithmType attribute not in the section but in . Anyway, please try the 5.80.140 build.
It can be downloaded from http://www.devart.com/dotconnect/mysql/download.html (trial version) or from Registered Users' Area (for users with valid subscription only).
For more information, please refer to http://www.devart.com/forums/viewtopic.php?t=18031 .
KW, please try this latest build. It seems like that the Unrecognized attribute:hashAlgorithmType error you have got when making a workaround was caused by setting the hashAlgorithmType attribute not in the section but in . Anyway, please try the 5.80.140 build.
Thank you.Shalex wrote:dotConnect for MySQL v 5.80 is released!
It can be downloaded from http://www.devart.com/dotconnect/mysql/download.html (trial version) or from Registered Users' Area (for users with valid subscription only).
For more information, please refer to http://www.devart.com/forums/viewtopic.php?t=18031 .
KW, please try this latest build. It seems like that the Unrecognized attribute:hashAlgorithmType error you have got when making a workaround was caused by setting the hashAlgorithmType attribute not in the section but in . Anyway, please try the 5.80.140 build.
OK, I am going to document this in a few places because the answer to my specific problem wasn’t anywhere to be found.
Longform:
The overt problem: The user logon code provided by Microsoft, Membership.ValidateUser stopped working after working for a number of months. The supporting code for this method was also “canned” and was largely plagiarized from Microsoft’s website, up to and including the remarks.
Collateral problems: I was heavily multitasking at the time, and changes had been made to numerous parts of the project, which clouded the symptoms of this problem.
Cause: I was creating a Development and Test version of the project and changed the web.config settings to point to the Development database. However, changing web.config back to production did not fix the problem. It did fix the intermediate problem with connections to the web services. Which was, of course a serious part of the problem. Deleting and restoring the entire solution from a known working backup did not fix the log on problem.
Final Solution: Edited copy of web.config at C:\Inetpub\wwwroot\YOURWEBPROJECTNAME\web.config,
I don’t know where the settings are that System.Web.Security.Membership points to the published location, vice the projects development location on G: Drive, or why publishing once caused the change, but republishing didn’t rewrite web.config.
Shortform:
Having problems with Membership.ValidateUser? Check the settings to ALL your web.config files, even ones you don't know you have.
Longform:
The overt problem: The user logon code provided by Microsoft, Membership.ValidateUser stopped working after working for a number of months. The supporting code for this method was also “canned” and was largely plagiarized from Microsoft’s website, up to and including the remarks.
Collateral problems: I was heavily multitasking at the time, and changes had been made to numerous parts of the project, which clouded the symptoms of this problem.
Cause: I was creating a Development and Test version of the project and changed the web.config settings to point to the Development database. However, changing web.config back to production did not fix the problem. It did fix the intermediate problem with connections to the web services. Which was, of course a serious part of the problem. Deleting and restoring the entire solution from a known working backup did not fix the log on problem.
Final Solution: Edited copy of web.config at C:\Inetpub\wwwroot\YOURWEBPROJECTNAME\web.config,
I don’t know where the settings are that System.Web.Security.Membership points to the published location, vice the projects development location on G: Drive, or why publishing once caused the change, but republishing didn’t rewrite web.config.
Shortform:
Having problems with Membership.ValidateUser? Check the settings to ALL your web.config files, even ones you don't know you have.