I have just upgraded to openfire 3.4.3 from wildfire 3.0.1 (via 3.2.0) and everything appears to work, apart from logging into the HTTPS admin console. The login page is display prompting for username/password, but upon entering these the page just hangs.
Strangly, I can authenticate via plain HTTP.
My jabber connections to the server work fine.
Openfire is running on RHEL4 via Sun’s JRE 1.5.0_09. My user accounts are specified via LDAP (over SSL) as are the admin accounts. I imported my SSL certificate from my wildfire install, which did only contain the public/private keypair provided by my registrar, as well as the rest of the certificate chain to get to their root CA. The keystore doesn’t contain the CA for the LDAP though (but either Openfire does validate the cert chain for that anyhow, or I haven’t switched it on).
Attempts to log into the admin console via HTTPS don’t show up in the LDAP access log, but those from HTTP/jabber do.
I tested with before upgrading with jdk1.5.0_13, and this appeared to work fine (although it was on a different machine so may not be the only difference).
I have the same problem. Strangely, it seems that if you login with http, you can then switch to https and everything will work find. It narrows it down to something in the login process. Also, I do not get this behavior when using Safari (on a Mac, obviously). I can login with no problem whatsoever.
After your suggestion I switched from Firefox 1.5.0.12 (Centos) and Konquerer (3.5.4-13.6.el5.centos) to trying Opera 9.23 (linux) and that handled the https login fine.
Trying IE6 on Windows works okay as well. So I guess it’s a client browser issue.
I just upgraded to Openfire 3.4.4 from 3.4.2 (this was done by moving the old /opt/openfire directory to /opt/oldopenfire and then untarring the new one into /opt/openfire (so that all the startup scripts point to the same place).
I then copied the old openfire.xml into the conf directory of the new install.
I use openLDAP to authenticate.
I have no problem authenticating the users via http for the admin console (and do this via a ssh tunnel to keep it secure) - but via https it just doesn’t want to work.
I am using gentoo on client and server. SSL connections work for the jabber client (in my case pidgin).