authelia/docs/content/en/integration/openid-connect/synapse/index.md

2.7 KiB

title description lead date draft images menu weight toc community
Synapse Integrating Synapse with the Authelia OpenID Connect Provider. 2022-06-15T17:51:47+10:00 false
integration
parent
openid-connect
620 true true

Tested Versions

Before You Begin

Common Notes

  1. You are required to utilize a unique client id for every client.
  2. The client id on this page is merely an example and you can theoretically use any alphanumeric string.
  3. You should not use the client secret in this example, We strongly recommend reading the Generating Client Secrets guide instead.

Assumptions

This example makes the following assumptions:

  • Application Root URL: https://matrix.example.com/
  • Authelia Root URL: https://auth.example.com
  • Client ID: synapse
  • Client Secret: synapse_client_secret

Configuration

Application

To configure Synapse to utilize Authelia as an OpenID Connect 1.0 Provider:

  1. Edit your Synapse homeserver.yaml configuration file and add configure the following:
oidc_providers:
  - idp_id: authelia
    idp_name: "Authelia"
    idp_icon: "mxc://authelia.com/cKlrTPsGvlpKxAYeHWJsdVHI"
    discover: true
    issuer: "https://auth.example.com"
    client_id: "synapse"
    client_secret: "synapse_client_secret"
    scopes: ["openid", "profile", "email"]
    allow_existing_users: true
    user_mapping_provider:
      config:
        subject_claim: "sub"
        localpart_template: "{{ user.preferred_username }}"
        display_name_template: "{{ user.name }}"
        email_template: "{{ user.email }}"

Authelia

The following YAML configuration is an example Authelia client configuration for use with Synapse which will operate with the above example:

- id: synapse
  description: Synapse
  secret: '$plaintext$synapse_client_secret'
  public: false
  authorization_policy: two_factor
  redirect_uris:
    - https://synapse.example.com/_synapse/client/oidc/callback
  scopes:
    - openid
    - profile
    - email
  userinfo_signing_algorithm: none

See Also