Table of Contents

Single-Sign-On into Matomo using Admidio as an OpenID Provider

Starting with version 5.0, Admidio can be used by other applications to authenticate users against Admidio's user base. These instructions will guide you through the process of connecting Matomo to Admidio to use Admidio's login. For general instructions, and other apps, please visit the general Single-Sign-On overview page.

Matomo provides OpenID Connect login through the Login OIDC or its fork RebelOIDC plugins. Both plugins are free and work similarly. RebelOIDC is a relatively recent fork to fix some long-standing issues in LoginOIDC. On the other hand, LoginOIDC has a longer history and a larger user base. Both of them are good choices, and the configuration is similar. The only difference so far is that in the redirect URL for RebelOIDC the string LoginOIDC must be replaced with RebelOIDC.

Prerequisites

Throughout the document we will assume you have both Admidio and Matomo already set up properly at https://admidio.local/ and https://matomo.local/. Please modify these URLs to your actual installation.

As a first step, one needs to configure Admidio to act as an OpenID Provider (OP). This has to be done once and is not specific to Matomo. Please follow this guide: #a_basic_setup_for_admidio_as_an_oidc_id_provider

Basically, one (1) needs to create a cryptographic key to sign message and choose a unique EntityID. The page https://admidio.local/adm_program/modules/preferences.php?panel=sso also provides the link to the metadata xml, and the individual settings in case a client does not support auto-configuration via metadata.

Quick Overview

Setting up Matomo (OpenID “Relying Party” - short RP) to use Admidio's user accounts for logging in consists of two steps: (1) Matomo needs to be set up with the data about the OpenID Provider (OP). One has to manually paste the Admidio endpoint URLs of the OpenID provider into the client's configuration. (2) Admidio needs to be told about the client. In particular, the entity ID and the redirect URL must be given, and a custom-generated (random) secret must be copied to the client configuration.

The concrete steps are:

Matomo Login via OpenID using the Login OIDC plugin (LoginOIDC)

Configuring the IdP settings for the Relying Party (Matomo)

Setting up the Client (RP) in Admidio

After saving the changes (both in Matomo and Admidio), the apps should should now be set up for single-sign-on in Matomo.

Setup completed, test Single-Sign-On

Admidio and Matomo should now be set up to use Admidio for logging in to Matomo. If you log out of Matomo and try to log in again, you will be shown the Admidio login screen and then redirected back to Matomo after a successful login.

If a new user logs in, a new user account is created (if the corresponding config setting is selected), but the new user will not have any permissions and an error will be displayed. A Matomo admin must assign the correct permissions to the new user. This can be done in the Matomo user config section. Superuser permissions cannot be assigned in the list, but one can open the user for editing with the icon on the right:

Once the user has access permissions to a page, the successfull login will show the analytics page of Matomo:

1)
Admidio will create a secure client secret and allow it to be copied to the client. Afterwards it is only stored as a hash in the database and not be recovered any more. However, one can create a new Client Secret in Admidio and copy that to the client's configuration.