Nothing has changed in a long time in terms of ldap or other authentication. 

You need to make sure you keep the same machine key in web.config whenever you upgrade, you need to copy it from the old web.config to the new one. Not doing that could break authentication.

Hope that helps,

Joe

I would check the log for any clues

/Data/currentlog.config

I worked on the LDAP fallback code, and have a Microsoft domain I can test with, so let me download and test using the latest codeline and I'll report back.

Are you using Active Directory authentication or true LDAP?

Jamie

I just tested in our environment and everything seems to be working correctly. I tried the following scenarios:

• LDAP user (administrator)
• Non-LDAP user with local DB authentication fallback (login by username)
• Non-LDAP user with local DB authentication fallback (login by email address)

In my testing I did get the same LDAP failure errors logged when logging in as a local DB user. This is expected, however, because at the time of attempted LDAP login, it's not known if they are an LDAP or local user. So seeing those messages appear in your log is normal.

Unfortunately I don't have the ability to test against a true LDAP server, but as Joe said, that portion of the code has not been modified for a very long time (years).

Are you getting a login failure message displayed in mojoPortal, or does it just appear that nothing is happening? I've seen the latter occur with a misconfiguration of SSL settings.

Jamie

If no error is logged when you attempt signing in as a domain user, that should indicate that LDAP authentication succeeded. I'm not sure what would cause mojoPortal to then fail the login after that point. Hopefully Joe has some other ideas up his sleeve.

Just as a long shot, can you verify that the users you are testing with are not flagged as locked out? Or is it possible that they are under temporary lockout due to too many failed logins before you restored the machine key?

Jamie