Ldap: Invalid username or password

I recently deployed openfire 3.7.0. I’m running on Ubuntu server 10.04 x64. I was able to get active directory authentication (LDAP) setup properly and users can connect using their AD credentials. However, after a couple of hours, the ldap authentication breaks and no one can login; users get an error “Invalid username or password”. Users are using Spark v 2.6.3. Reinstalling the Spark client does not fix the issue.

Rebooting the openfire service does not fix the issue, but rebooting the entire server does fix the issue temporarily.

I have about 125 users connected at any given time. Here are the log file errors:

at org.jivesoftware.util.LocaleUtils.getLocalizedString(LocaleUtils.java:489)
at org.jivesoftware.util.LocaleUtils.getLocalizedString(LocaleUtils.java:440)
at org.jivesoftware.util.LocaleUtils.getLocalizedString(LocaleUtils.java:424)
at org.jivesoftware.admin.AdminConsole.getAdminText(AdminConsole.java:239)
at org.jivesoftware.admin.SubnavTag.doEndTag(SubnavTag.java:182)
at org.jivesoftware.openfire.admin.decorators.main_jsp.jspx_meth_admin_subnavbar 0(main_jsp.java:387)
at org.jivesoftware.openfire.admin.decorators.main_jsp._jspService(main_jsp.java:2 22)

at org.jivesoftware.util.LocaleFilter.doFilter(LocaleFilter.java:74)
at org.jivesoftware.util.SetCharacterEncodingFilter.doFilter(SetCharacterEncodingF ilter.java:50)
at org.jivesoftware.admin.PluginFilter.doFilter(PluginFilter.java:78)
at org.jivesoftware.admin.AuthCheckFilter.doFilter(AuthCheckFilter.java:164)

Rebooting the server every few hours is not a viable long-term solution. Can anyone please provide some assistance?

Thank you.

Having a very similar issue. Occasionly logging into openfire/spark will fail numerous times in a row. I googled one of the error codes in the log and found this page…

Can anyone resolve this? It’s causing huge (embaressing) problems when clients are complaining they’re unable to login and then we face the same problem when trying to connect to the openfire admin console to try and diagnose.

This is a coding error, I very much doubt it’s an issue with the config (which has worked flawlessly for myself) or the client. Although I did see on a seperate forum that it maybe AD related, I’d like someone to confirm either way please.

I was able to resolve this by doing 2 things:

  1. Using a Windows Server 2008 domain controller for AD authentication.

  2. Creating an entry in the hosts files that points to the domain controller.

I’ll try the hosts file thing (doubt this will work). I think the AD upgrade will of resolved your issue actually, something that’s not really plausable for our business at this point in time. I’ll see anyway.

Thanks for your response, frankly any response is useful