Hi,

I did find and fix a bug, it seems to have been introduced during some work on support for fallback to database authentication when using LDAP. The changes was causing it to fail to increment the failed password attempt count.

If you look in Web/Components/mojoMembershipProvider.cs in the ValidateUser method, find this code:

string user;
if (!siteSettings.UseLdapAuth || (siteSettings.UseLdapAuth && WebConfigSettings.UseLDAPFallbackAuthentication))
{
user = SiteUser.Login(siteSettings, userName, encPassword);
if ((user != null) && (user != String.Empty))
{
  result = true;
  siteUser = new SiteUser(siteSettings, userName);
}
}

and change it like this:

string user;
if (!siteSettings.UseLdapAuth || (siteSettings.UseLdapAuth && WebConfigSettings.UseLDAPFallbackAuthentication))
{
user = SiteUser.Login(siteSettings, userName, encPassword);
if ((user != null) && (user != String.Empty))
{
  result = true;
  siteUser = new SiteUser(siteSettings, userName);
}
else if (!siteSettings.UseLdapAuth)
{
  // need to create the user here so we can increment the failed password attmpt count below
  siteUser = new SiteUser(siteSettings, userName);
}
}

Hope that helps,

Joe

That file gets compiled into mojoPortal.Web.dll

you can't just update specific files unless your source code corresponds exactly to compiled files you have deployed, then you could make a small change and just deploy the changed file but you obviously have a different version deployed than what you have for source code so deploying just one file will break things because it is a version mismatch and not compatible. You need to either use source code that corresponds to your current deployment or you need to deploy everything to make a full deployment package. See Packaging and Deployment for steps I use to make a deployment package.

those changeset download links are not a reliable way to get the source code, the correct way is to use TortoiseHG

if you clone the repository using TortoiseHG, in the clone Options choose Clone to revision and enter 1664 as the revision number then you will have a correct local copy of the source code for version 2.3.6.5

Hope that helps,

Joe