2022-06-15 07:51:47 +00:00
---
title: "Synapse"
2022-07-01 03:07:02 +00:00
description: "Integrating Synapse with the Authelia OpenID Connect Provider."
2022-06-15 07:51:47 +00:00
lead: ""
2022-06-28 05:27:14 +00:00
date: 2022-06-15T17:51:47+10:00
2022-06-15 07:51:47 +00:00
draft: false
images: []
menu:
integration:
parent: "openid-connect"
weight: 620
toc: true
community: true
---
## Tested Versions
* [Authelia]
* [v4.35.6 ](https://github.com/authelia/authelia/releases/tag/v4.35.6 )
* [Synapse]
* [v1.60.0 ](https://github.com/matrix-org/synapse/releases/tag/v1.60.0 )
## Before You Begin
2023-02-02 01:30:06 +00:00
{{% oidc-common %}}
2022-10-20 04:42:22 +00:00
2022-10-20 04:27:09 +00:00
### Assumptions
2022-06-15 07:51:47 +00:00
This example makes the following assumptions:
* __Application Root URL:__ `https://matrix.example.com/`
* __Authelia Root URL:__ `https://auth.example.com`
* __Client ID:__ `synapse`
2023-02-02 01:30:06 +00:00
* __Client Secret:__ `insecure_secret`
2022-06-15 07:51:47 +00:00
## Configuration
### Application
2023-01-25 23:59:18 +00:00
To configure [Synapse] to utilize Authelia as an [OpenID Connect 1.0] Provider:
2022-06-15 07:51:47 +00:00
1. Edit your [Synapse] `homeserver.yaml` configuration file and add configure the following:
```yaml
oidc_providers:
2022-07-29 05:29:58 +00:00
- idp_id: authelia
2022-06-15 07:51:47 +00:00
idp_name: "Authelia"
2022-07-29 05:29:58 +00:00
idp_icon: "mxc://authelia.com/cKlrTPsGvlpKxAYeHWJsdVHI"
discover: true
2022-06-15 07:51:47 +00:00
issuer: "https://auth.example.com"
client_id: "synapse"
2023-02-02 01:30:06 +00:00
client_secret: "insecure_secret"
2022-07-29 01:03:10 +00:00
scopes: ["openid", "profile", "email"]
2022-07-29 05:29:58 +00:00
allow_existing_users: true
2022-06-15 07:51:47 +00:00
user_mapping_provider:
config:
2022-07-29 01:03:10 +00:00
subject_claim: "sub"
localpart_template: "{{ user.preferred_username }}"
display_name_template: "{{ user.name }}"
email_template: "{{ user.email }}"
2022-06-15 07:51:47 +00:00
```
### Authelia
The following YAML configuration is an example __Authelia__
2023-05-15 00:32:10 +00:00
[client configuration ](../../../configuration/identity-providers/openid-connect/clients.md ) for use with [Synapse]
2022-06-15 07:51:47 +00:00
which will operate with the above example:
```yaml
2023-04-02 03:12:01 +00:00
identity_providers:
oidc:
## The other portions of the mandatory OpenID Connect 1.0 configuration go here.
## See: https://www.authelia.com/c/oidc
clients:
2023-05-07 06:39:17 +00:00
- id: 'synapse'
description: 'Synapse'
2023-04-02 03:12:01 +00:00
secret: '$pbkdf2-sha512$310000$c8p78n7pUMln0jzvd4aK4Q$JNRBzwAo0ek5qKn50cFzzvE9RXV88h1wJn5KGiHrD0YKtZaR/nCb2CJPOsKaPK0hjf.9yHxzQGZziziccp6Yng' # The digest of 'insecure_secret'.
public: false
2023-05-07 06:39:17 +00:00
authorization_policy: 'two_factor'
2023-04-02 03:12:01 +00:00
redirect_uris:
2023-05-07 06:39:17 +00:00
- 'https://synapse.example.com/_synapse/client/oidc/callback'
2023-04-02 03:12:01 +00:00
scopes:
2023-05-07 06:39:17 +00:00
- 'openid'
- 'profile'
- 'email'
2023-05-15 00:32:10 +00:00
userinfo_signing_alg: 'none'
2022-06-15 07:51:47 +00:00
```
## See Also
* [Synapse OpenID Connect Authentication Documentation ](https://matrix-org.github.io/synapse/latest/openid.html )
[Authelia]: https://www.authelia.com
[Synapse]: https://github.com/matrix-org/synapse
2023-01-25 23:59:18 +00:00
[OpenID Connect 1.0]: ../../openid-connect/introduction.md