From b95eb6dee8f84f4c6eb366301d73c3b89622db2c Mon Sep 17 00:00:00 2001 From: MatMaul Date: Mon, 15 May 2023 09:18:24 +0000 Subject: deploy: aa5c0592e72e7ef8c015208e9947b385e6a87e59 --- develop/print.html | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) (limited to 'develop/print.html') diff --git a/develop/print.html b/develop/print.html index 292e4c58fc..6e4bf95dcb 100644 --- a/develop/print.html +++ b/develop/print.html @@ -8235,7 +8235,7 @@ This can be optionally enabled by setting backchannel_logout_enabledYou should receive a response similar to the following. Make sure to save it.

{"client_id":"someclientid_123","client_secret":"someclientsecret_123","id":"12345","name":"my_synapse_app","redirect_uri":"https://[synapse_public_baseurl]/_synapse/client/oidc/callback","website":null,"vapid_key":"somerandomvapidkey_123"}
 
-

As the Synapse login mechanism needs an attribute to uniquely identify users, and Mastodon's endpoint does not return a sub property, an alternative subject_claim has to be set. Your Synapse configuration should include the following:

+

As the Synapse login mechanism needs an attribute to uniquely identify users, and Mastodon's endpoint does not return a sub property, an alternative subject_template has to be set. Your Synapse configuration should include the following:

oidc_providers:
   - idp_id: my_mastodon
     idp_name: "Mastodon Instance Example"
@@ -8249,7 +8249,9 @@ This can be optionally enabled by setting backchannel_logout_enabled

Note that the fields client_id and client_secret are taken from the CURL response above.

Shibboleth with OIDC Plugin

-- cgit 1.5.1