XMPP real time collaboration server
Project homepage: https://www.igniterealtime.org/projects/openfire/index.jsp
Description
Openfire is a real time collaboration (RTC) server licensed under the
GPL. 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.
Package information
- Ports path
- net/openfire
- Package architecture
- amd64
- Maintainer
- Ian Darwin <ian@openbsd.org>
- Categories
- net, java
- Available flavors
- None listed
- Only for architectures
- i386, amd64, aarch64
Ports list build and test dependencies as well as runtime dependencies. pkg_add selects those needed for installation.
Direct dependencies
Runtime
- java/javaPathHelper
- devel/jdk/17 jdk->=17v0,<18v0
OpenBSD README
This README contains unresolved ports variables; replace them before using its commands.
+-----------------------------------------------------------------------
| Running openfire on OpenBSD
+-----------------------------------------------------------------------
1) openfire requires a database. If you intend on using the embedded
(HSQLDB) database you may skip to step #2. If you intend on using
MySQL or PostgreSQL, instructions are available at:
${TRUEPREFIX}/share/doc/openfire/database.html
2) openfire may be started by executing:
rcctl start openfire
as root. To arrange for this to happen at boot, add 'openfire'
to "pkg_scripts" in /etc/rc.conf.local(8):
rcctl enable openfire
3) After starting openfire, you may access the web interface at
http://[hostname]:9090/; when you first login there is a configuration
dialog. After enabling SSL, you can use https://[hostname]:9091/
When creating the admin account, note that the default username
is "admin", not the email address you enter.
4) openfire's automated setup and plugin installation services require
several directories to be writable by the _openfire user. When you
complete the installation process, you may wish to tighten permissions
on ${TRUEPREFIX}/openfire and its subdirectories.
5) openfire's DIGEST-MD5 SASL mechanism does not interoperate very well.
If you experience issues with client authentication, you may need to
force the SASL mechanism to PLAIN by adding:
<sasl><mechs>PLAIN</mechs></sasl>
as the second-last line of ${TRUEPREFIX}/openfire/conf/openfire.xml
(e.g, just inside the closing XML tag).
Then restart openfire for the changes to take effect.