mirror of
https://github.com/element-hq/synapse
synced 2024-08-19 19:40:20 +00:00
deploy: aa5c0592e7
This commit is contained in:
parent
63c6795ad2
commit
b95eb6dee8
4 changed files with 10 additions and 6 deletions
|
@ -655,7 +655,7 @@ This can be optionally enabled by setting <code>backchannel_logout_enabled</code
|
||||||
<p>You should receive a response similar to the following. Make sure to save it.</p>
|
<p>You should receive a response similar to the following. Make sure to save it.</p>
|
||||||
<pre><code class="language-json">{"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"}
|
<pre><code class="language-json">{"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"}
|
||||||
</code></pre>
|
</code></pre>
|
||||||
<p>As the Synapse login mechanism needs an attribute to uniquely identify users, and Mastodon's endpoint does not return a <code>sub</code> property, an alternative <code>subject_claim</code> has to be set. Your Synapse configuration should include the following:</p>
|
<p>As the Synapse login mechanism needs an attribute to uniquely identify users, and Mastodon's endpoint does not return a <code>sub</code> property, an alternative <code>subject_template</code> has to be set. Your Synapse configuration should include the following:</p>
|
||||||
<pre><code class="language-yaml">oidc_providers:
|
<pre><code class="language-yaml">oidc_providers:
|
||||||
- idp_id: my_mastodon
|
- idp_id: my_mastodon
|
||||||
idp_name: "Mastodon Instance Example"
|
idp_name: "Mastodon Instance Example"
|
||||||
|
@ -669,7 +669,9 @@ This can be optionally enabled by setting <code>backchannel_logout_enabled</code
|
||||||
scopes: ["read"]
|
scopes: ["read"]
|
||||||
user_mapping_provider:
|
user_mapping_provider:
|
||||||
config:
|
config:
|
||||||
subject_claim: "id"
|
subject_template: "{{ user.id }}"
|
||||||
|
localpart_template: "{{ user.username }}"
|
||||||
|
display_name_template: "{{ user.display_name }}"
|
||||||
</code></pre>
|
</code></pre>
|
||||||
<p>Note that the fields <code>client_id</code> and <code>client_secret</code> are taken from the CURL response above.</p>
|
<p>Note that the fields <code>client_id</code> and <code>client_secret</code> are taken from the CURL response above.</p>
|
||||||
<h3 id="shibboleth-with-oidc-plugin"><a class="header" href="#shibboleth-with-oidc-plugin">Shibboleth with OIDC Plugin</a></h3>
|
<h3 id="shibboleth-with-oidc-plugin"><a class="header" href="#shibboleth-with-oidc-plugin">Shibboleth with OIDC Plugin</a></h3>
|
||||||
|
|
|
@ -8235,7 +8235,7 @@ This can be optionally enabled by setting <code>backchannel_logout_enabled</code
|
||||||
<p>You should receive a response similar to the following. Make sure to save it.</p>
|
<p>You should receive a response similar to the following. Make sure to save it.</p>
|
||||||
<pre><code class="language-json">{"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"}
|
<pre><code class="language-json">{"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"}
|
||||||
</code></pre>
|
</code></pre>
|
||||||
<p>As the Synapse login mechanism needs an attribute to uniquely identify users, and Mastodon's endpoint does not return a <code>sub</code> property, an alternative <code>subject_claim</code> has to be set. Your Synapse configuration should include the following:</p>
|
<p>As the Synapse login mechanism needs an attribute to uniquely identify users, and Mastodon's endpoint does not return a <code>sub</code> property, an alternative <code>subject_template</code> has to be set. Your Synapse configuration should include the following:</p>
|
||||||
<pre><code class="language-yaml">oidc_providers:
|
<pre><code class="language-yaml">oidc_providers:
|
||||||
- idp_id: my_mastodon
|
- idp_id: my_mastodon
|
||||||
idp_name: "Mastodon Instance Example"
|
idp_name: "Mastodon Instance Example"
|
||||||
|
@ -8249,7 +8249,9 @@ This can be optionally enabled by setting <code>backchannel_logout_enabled</code
|
||||||
scopes: ["read"]
|
scopes: ["read"]
|
||||||
user_mapping_provider:
|
user_mapping_provider:
|
||||||
config:
|
config:
|
||||||
subject_claim: "id"
|
subject_template: "{{ user.id }}"
|
||||||
|
localpart_template: "{{ user.username }}"
|
||||||
|
display_name_template: "{{ user.display_name }}"
|
||||||
</code></pre>
|
</code></pre>
|
||||||
<p>Note that the fields <code>client_id</code> and <code>client_secret</code> are taken from the CURL response above.</p>
|
<p>Note that the fields <code>client_id</code> and <code>client_secret</code> are taken from the CURL response above.</p>
|
||||||
<h3 id="shibboleth-with-oidc-plugin"><a class="header" href="#shibboleth-with-oidc-plugin">Shibboleth with OIDC Plugin</a></h3>
|
<h3 id="shibboleth-with-oidc-plugin"><a class="header" href="#shibboleth-with-oidc-plugin">Shibboleth with OIDC Plugin</a></h3>
|
||||||
|
|
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
Loading…
Reference in a new issue