Overview

XMPP chat client

To Access

From the Community Admin page, click the XMPP tab.

XMPP is a chat protocol that enables users to have instant message applications and other technologies. Support in Tiki was first added in 2003, as shown in this commit. Today, XMPP support in Tiki relies on the ConverseJS XMPP client, which provides a modern web based chat interface. Using this integration, Tiki users can add real time chat features directly to their websites. See also PluginXMPP and Module XMPP.

Tiki provides real time chat features through the XMPP protocol. XMPP is an open and widely used standard for instant messaging and group communication. In Tiki, XMPP is used to enable both private conversations and shared chatrooms directly within the web interface.

Tiki does not act as an XMPP server. It relies on an external XMPP server to handle message delivery, presence, and chatroom management. The web based chat interface is provided by ConverseJS, which runs in the user’s browser and connects to the XMPP server.

XMPP integration allows a Tiki site to offer interactive communication features without relying on proprietary services. Users can exchange direct messages, participate in group discussions, and interact in real time. Anonymous visitors can also join public chatrooms, which makes XMPP suitable for support, community discussions, and live collaboration.

Because Tiki manages users and groups, it can automatically control access to chatrooms and authentication. This ensures that chat behavior remains consistent with the site’s permission model.

The XMPP setup in Tiki involves several components working together. Tiki manages users, groups, and permissions, while the XMPP server is responsible for messaging and chatroom logic. ConverseJS acts as the client inside the browser and connects to the XMPP server using standard XMPP protocols.

Desktop and mobile XMPP clients can connect to the same server. This allows administrators or power users to participate in conversations without using the web interface.

A working XMPP setup requires an operational XMPP server, a domain name, and valid TLS certificates to ensure secure communication. On the Tiki side, you need a recent version with RTC and XMPP features enabled, as well as access to the administration panels.

This feature assumes a basic level of server administration knowledge, especially for DNS and certificate management.

Tiki can connect to several XMPP servers, but Prosody is the recommended option. It is lightweight, actively maintained, and well tested with Tiki. Other servers such as Openfire, ejabberd, or Tigase can also be used, but they require different integration approaches and may not be fully documented for Tiki.

For most use cases, Prosody offers the simplest and most reliable experience.

Use the following guide to install Prosody and connect it to Tiki’s user system:
https://wikisuite.org/How-to-install-Prosody-using-Tiki-for-its-userlist

That guide explains how to install Prosody, enable HTTP authentication with Tiki, support anonymous users, configure chatrooms, and secure the setup using TLS. It is written to work specifically with Tiki and should be followed step by step.

Once the XMPP server is ready, configuration continues inside Tiki. In the Admin Control Panels, under RTC and XMPP, you define how Tiki connects to the XMPP server. This includes the XMPP domain, the BOSH or WebSocket endpoint, and the authentication method.

These settings allow Tiki to automatically authenticate users, display the ConverseJS interface, and manage chatroom access based on group membership. No manual login is required for users once the configuration is complete.

The integrated ConverseJS web client can be used in three distinct modes, depending on the desired user experience and placement.

Overlayed Mode is configured as a Tiki Module. A small box will appear on the bottom corner of the page containing a contact list. Users can click on contact list to start a chat session while simultaneously browsing the site.

The Embedded mode can be configured as a wiki plugin (PluginXMPP). A chatbox will appear directly in the middle of the page content where the plugin is placed. This is typically used for persistent group chats (MUC) dedicated to the specific topic of that page.

Fullscreen mode takes all webpage space to provide a comprehensive interface for contact lists and chat boxes, similar to a dedicated desktop application. Users can easily switch between private chats and group chats while using this mode.

The following examples illustrate common ways XMPP is used in a Tiki site. They show how different types of users interact with chat based on their roles and permissions.

• Alice is an anonymous visitor. She opens the site and immediately sees the ConverseJS chat interface. She asks a question in a public chatroom without creating an account. This allows visitors to interact with the community or support team instantly.

• Bob is a registered user. When he logs in to Tiki, he is automatically authenticated in XMPP. He is added to the Registered chatroom without any manual action. Chat access matches his site permissions.

• Charlie is a translator. He is a registered user and belongs to the Translators group in Tiki. When he logs in, he joins both the Registered chatroom and the Translators chatroom. Group membership controls which conversations he can access.

• Dan is a technical user who already owns an external XMPP account. He configures his own JID in Tiki. He continues to join Tiki chatrooms while keeping his external identity. This allows advanced users to reuse existing XMPP setups.

• Eve is an administrator. She uses Gajim on her desktop to connect to the same XMPP server. She joins the chatrooms and answers questions from anonymous visitors. She can moderate discussions without opening the Tiki web interface.

Tiki groups are mapped directly to XMPP chatrooms. When a user joins or leaves a group in Tiki, their access to the corresponding chatroom is updated automatically. This ensures that chat permissions remain consistent with site permissions at all times.

This approach reduces administrative effort and avoids manual room management on the XMPP server.

When using XMPP with Multi-User Chat (MUC) auto-join based on Tiki groups, room memberships are synchronized asynchronously between Tiki, the XMPP server (Prosody), and the Converse.js client.

As a result, during login or immediately after registration, a user may not directly see the popup for chatrooms they should be in.

This is expected behavior and usually resolves automatically within a few seconds as the systems sync. If needed, a simple page reload will finalize the room membership. This design avoids blocking the user interface while ensuring correct and scalable synchronization.

The primary chat interface in Tiki is ConverseJS, which runs in the browser. In addition, users can connect using desktop clients such as Gajim or mobile XMPP clients. All clients connect to the same XMPP server and share the same chatrooms, which provides flexibility without duplicating configuration.

XMPP integration in Tiki requires server level configuration and is not a plug and play feature. Administrators must manage DNS, certificates, and the XMPP server itself.

The XMPP Prebind library candy-chat/xmpp-prebind-php allows Tiki to perform automatic login to an XMPP server using the Openfire TikiToken authentication method. This makes the user experience smoother because users do not have to type their username and password to join the chat.

Importance:

• Required only for the TikiToken authentication method.
• Not needed for Username/Password or OAuthBearer Token authentication.
• If you select TikiToken in the admin settings but the library is not installed, Tiki will still work: ConverseJS will fall back to standard BOSH login, and users can still access chat. No warning appears in the admin UI.

  
  

Installation steps:

1. Open a terminal and go to your Tiki installation folder.
2. Require the library using Composer:

composer require candy-chat/xmpp-prebind-php

1. Composer will download and install the library.
2. After installation, Tiki will detect the library automatically. The class `XmppPrebind` will now be available.
3. Go to Admin home > RTC > XMPP and select the TikiToken authentication method. The prebind library will be used automatically.

New in Tiki17: the addition of the ConverseJS XMPP client.
New in Tiki19: PluginXMPP to embed a chatroom in a wiki page

The reference implementation is with Openfire, but this should work with any XMPP server (perhaps with fewer features).

• Converse.js
• ConverseJS
• Converse JS