Planning the installation

This part of the documentation goes through installing the service, the important parts of the configuration file, and how to run the service.

Before going through the installation, it is important to understand the different components of an OIDC-native Matrix homeserver, and how they interact with each other. It is meant to complement the homeserver, replacing the internal authentication mechanism with the authentication service.

Making a homeserver deployment OIDC-native radically shifts the authentication model: the homeserver is no longer responsible for managing user accounts and sessions. The authentication service becomes the source of truth for user accounts and access tokens, and the homeserver only verifies the validity of the tokens it receives through the service.

At time of writing, the authentication service is meant to be run on a standalone domain name (e.g., and the homeserver on another (e.g. This domain will be user-facing as part of the authentication flow.

When a client initiates an authentication flow, it will discover the authentication service through the deployment .well-known/matrix/client endpoint. This file will refer to an issuer, which is the canonical name of the authentication service instance. Out of that issuer, it will discover the rest of the endpoints by calling the [issuer]/.well-known/openid-configuration endpoint. By default, the issuer will match the root domain where the service is deployed (e.g., but it can be configured to be different.

An example setup could look like this:

  • The deployment domain is, so Matrix IDs look like

  • The issuer chosen is

  • The homeserver is deployed on

  • The authentication service is deployed on

  • Calling returns the following JSON:

      "m.homeserver": {
        "base_url": ""
      "org.matrix.msc2965.authentication": {
        "issuer": "",
        "account": ""
  • Calling returns a JSON document similar to the following:

        "issuer": "",
        "authorization_endpoint": "",
        "token_endpoint": "",
        "jwks_uri": "",
        "registration_endpoint": "",
        "//": "..."

With the installation planned, it is time to go through the installation and configuration process. The first section focuses on installing the service.