I’ve successfully setup Openfire and Spark IM client are able to login and chat locally.
I tried to NAT the local IP to a WAN IP. Tested it by putting in the WAN :9090 and :7070 both are accessible but whenever I used the application it just says
invalid username or password.
FYI: I’ve attached this to an ldap to use Windows credentials
What version of Spark? 2.8.0 is using Smack 4 library, which doesn’t allow login when server’s name and SSL certificates name do not match. When you use IP address for server address it tries to match IP to your real server’s name.
Yes. 2.8.0, so is there a fix or workaround? I tried to host my external IP so that I won’t be using IP aadress instead use a domain name. When I ping the domain name, it point’s to the correct WAN IP but when I used the IM client, input the correct domain name, still invalid username and password
Do you have 5222 port forwarded? That’s what client uses. You can also try 2.7.7 version and see if it works better. Not sure if there will be a workaround for this as accepting not matching certificates is against security. In that case one might just disable TLS and use plain connections
And is it possible to show all exisiting Windows Accounts? I mean since this server is linked to our ldap, can it show all users regardless online or offline? or is it really has to be added manually?
I’m not using AD integration myself, so can’t help more. I think this depends on how your ldap filter was set during setup. It should be able to show AD groups there.
Previous I was not getting this to work inside my lan but after a few tweaks I just got 2.8.0 running ok.
The problem now is connecting via WAN.
I’m using two apps. Normal Spark, 2.8 and 2.7.7, and Xabber for Android.
With 2.7.7 and Xabber I can login fine, for now. With Openfire 4.1 all is going to change.
With 2.8 I can’t. No matter what I do, I simply can’t login. Maybe cause Server for WAN (I’m using a ddns domain to point to my real server ip) differs from the one used over lan.