Openfire 4.x and ClearOS 7.x
ClearOS is an operating system for your Server, Network, and Gateway systems. It is designed for homes, small to medium businesses, and distributed environments. ClearOS is commonly known as the Next Generation Small Business Server, while including indispensable Gateway and Networking functionality. It delivers a powerful IT solution with an elegant user interface that is completely web-based. Simply put.. ClearOS is the new way of delivering IT. Source: https://www.clearos.com/
Openfire is a real time collaboration (RTC) server licensed under the Open Source Apache License. It uses the only widely adopted open protocol for instant messaging, XMPP (also called Jabber). Openfire is incredibly easy to setup and administer, but offers rock-solid security and performance. Source: http://www.igniterealtime.org/projects/openfire/index.jsp
Openfire Meetings is an Openfire plugin that uses WebRTC and the Jitsi Videobridge to provide high quality, scalable video conferences for your Openfire users.You will also need the Openfire Meetings Chrome extension for screen sharing, co-browsing and application sharing. Source: https://www.igniterealtime.org/projects/openfire/plugins/ofmeet/readme.html
The Openfire Fastpath Plugin adds support for managed queued chat requests, such as a support team might use. For example, a web based "Live Support" interface can point a potential customer at a workgroup representing the Sales team. Members of that workgroup will receive notification that a someone is waiting and when someone from that workgroup accepts, the customer and the team member will be connected to communicate with each other.
To install Install Openfire on ClearOS within the WikiSuite environment follow the next steps.
1.- Install a fresh ClearOS Server, be sure to run the latest Software updates to the core system and include in the installation of:
a. The Web Server
b. Software Repository Modules
c. and Open LDAP and Directory Server
If not already installed, you may do so through the Webconfig-Market Place Module (https://your-ip-address:81/app/marketplace).
2.- Using Software Repository Module, make sure the clearos-epel, clearos-centos and clearos-centos-updates repositories are enable.
ClearOS's Firewall should configured to block all ports, and open the following:
TODO: list other ports
1.-Through the Webconfig-Open LDAP Directory Server Module (https://your-ip-address:81/app/openldap_directory).
2.-On the Directory Server Settings page set the server mode and Base Domain (https://your-ip-address:81/app/openldap_directory/settings/edit)
3.-On the Directory Server Policies page set the Publish Policy and Accounts access according to your requirements (https://your-ip-address:81/app/openldap_directory/policies/edit)
4.-Don't forget to create one or two users as they will be use in the Openfire configuration phase.
1.-Login to your ClearOS via SSH using root
2.-Install the Openfire RPM
Type:
rpm -ivh http://www.igniterealtime.org/downloadServlet?filename=openfire/openfire-4.0.0-1.i386.rpm
For Openfire to work on ClearOS 64-bit the 32-bit zlib library is required.
Source: https://community.igniterealtime.org/thread/43673
Type:
yum install zlib.i686
3.- Start the Openfire service:
Type:
/etc/init.d/openfire start
And check the status
/etc/init.d/openfire status
Use a web browser to connect to the admin console. The default port for the web-based admin console is 9091. Initial setup and administration can be done from a remote computer using LAN IP address instead or hostname if it is resolvable by the remote computer. i.e. https://your-ip-address:9091. Source: http://www.igniterealtime.org/builds/openfire/docs/latest/documentation/install-guide.html
1.-The first screen will request you to choose your preferred language and press continue.
2.-Type your host domain and press continue
3.-Select to use the Embedded Database and press continue
4.-Choose "Directory Server (LDAP)" as the user and group system to use with the server and press continue.
5.-Configure the connection settings for your LDAP directory and press "Test Settings"
6.-Once the test has been successful press "Save and Continue"
7.-Configure how the server finds and loads users from your LDAP directory and press "Test Settings"
8.-Once the test has been successful press "Save and Continue"
9.-Configure how the server finds and loads groups from your LDAP directory and press "Test Settings"
11.-Once the test has been successful press "Save and Continue"
12.-Choose one or more users from your LDAP directory to be administrators by entering their usernames. Press "Save and Continue"
13.-Setup is complete! Click on "Login to Admin Console"
14.-Log in to the Admin Console.
(as of 2016-01-31, this plugin has not been updated to work with 4.x but this should be resolved soon).
1.- Login to your Openfire Admin Console with a administrator user.
2.- Click on the Plugins Tab to manage Plugins
3.- Click on the available plugins link and scroll down to find the Openfire Meetings plugin
4.- Click on then ¨+¨ to add the plugin to the Openfire server
Source: http://www.igniterealtime.org/projects/openfire/plugins/ofmeet/readme.html
(please add documentation)
Here is a live example: http://avan.tech/Fastpath
and some notes from Guus (keep or delete what you think)
For future reference: the snippet is provided on the Openfire Admin Console (Fastpath - Workgroup Manager - Workgroup Settings - Text)
I have made jivelive.jsp available on http://evoludata.com:9090/webchat/jivelive.jsp - perhaps you'll need to edit the snippet above, if you're redirecting access to that resource through a reversed proxy.
There's a simple landing page here: http://evoludata.com:9090/webchat/
1.-There is no ClearOS group for the Openfire admins. Instead: Edit server properties: https://example.org:9091/server-properties.jsp
2.- Find the admin.authorizedJIDs property, edit it and add comma separated full JIDs. In our specific case user at example.org. "Click on Save Property"
3.- Openfire needs a restart, Login to your ClearOS via SSH using root and type:
service openfire restart
(see ClearOS doc)
As of Openfire 3.2 certificate management can be performed from the Admin Console. (And in 4.0, code has been revamped)
Once the setup process is completed Openfire will create self-signed certificates for the assigned Openfire's domain. Most users should either get the created certificates signed by a Certificate Authority or replace the created certificates with your own certificates. Source: http://www.igniterealtime.com/builds/openfire/docs/latest/documentation/ssl-guide.html
Question: As ClearOS also manages SSL certificates, how do they co-exist?