rafaelcaricio/gotosocial
1
0
Fork 0
forked from mirrors/gotosocial
Code Issues Pull requests Projects Releases Packages Wiki Activity

[docs] Clarify email requirement for OIDC (#1918)

Browse source
This commit is contained in:
Daenney 2023-06-21 21:22:51 +02:00 committed by GitHub
parent 8e0043104d
commit c4cf6326d8
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 3 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

3
docs/configuration/oidc.md
View file

@ -10,6 +10,9 @@ This is very convenient in the following cases:
- You want to delegate management of users, accounts, passwords etc. to an external service to make admin easier for yourself. - You want to delegate management of users, accounts, passwords etc. to an external service to make admin easier for yourself.
- You already have a lot of users in an external system and you don't want to have to recreate them all in GoToSocial manually. - You already have a lot of users in an external system and you don't want to have to recreate them all in GoToSocial manually.
!!! tip
If a user doesn't exist yet, login will fail if your IdP doesn't return a non-empty `email` as part of the claims. The email needs to be unique on this instance. Though we use the `sub` claim to associate the external identity with a GtS user, when a user is created it needs an email associated with it.
## Settings ## Settings
GoToSocial exposes the following configuration settings for OIDC, shown below with their default values. GoToSocial exposes the following configuration settings for OIDC, shown below with their default values.