I have just about every Linux distro that’s out there, (Debian, SuSe, Knoppix, Clark Connect, Redhat, Fedora, just to name a few), and I have tried every one of them on a test box, and only found Engarde as the easiest to operate and setup.
The best thing about Engarde is, using a small SELinux utility called ‘audit2allow’, one just installs an rpm using ‘rpm -ivh [prog-name-[version].rpm’ then run ‘watch audit2allow -d’ then run the prog, any security issues are then displayed as ‘allow’ lines, which then can be inserted into a custom policy, then the policy is re-compiled. All this I know how to do, but when it comes to fastpath’s webchat, there are no security issues even with SELinux completely disabled and no policies loaded, it just doesn’t know where to find the openfire server name, (see below for an explanation of an example server configuration).
I spent all day yesterday trying openfire on all the distros I have and the fastpath spark webchat still gives the same error, which indicates to me, that certain software for Linux is very version specific,
Here’s an example server configuration used for openfire.
server host name = test.com
openfire installs using that host name
Enterprise plugin installs, then spark webchat
Enterprise license is applied
Spark webchat setup is initiated
Openfire server name ‘test.com’ is inserted into the setup
Port 5222 is used
The ‘Save setup’ is clicked and nothing happens just an error stating ‘Can not connect to server, please make sure the host name and port is correct’, which indicates, openfire does know where to find the system host name, but spark webchat doesn’t know where to find openfire’s server name. People I’ve chatted to in either ignite and jive, can’t reproduce the same error, and therefore unable to find out how to fix it.
Use ‘localhost’ throughout the openfire and fastpath spark webchat setup, and everything is fine, except the group chat doesn’t work.
This is how it works:-
Fix groupchat and fastpath webchat don’t work, fix fastpath and the groupchat don’t work, there doesn’t seem to be any interactivity between the modules, if it’s a DNS issue, then the only possible explanation I can think of is, Engarde uses named to for bind configuration, and if spark webchat for fastpath is trying to obtain a record from a bind configuration, then it’s not going to work, which brings us back to being version specific.