docs/content/integration/openid-connect/clients/go-to-social/index.md
{{% oidc-common bugs="claims-hydration" %}}
This example makes the following assumptions:
https://gotosocial.{{< sitevar name="domain" nojs="example.com" >}}/https://{{< sitevar name="subdomain-authelia" nojs="auth" >}}.{{< sitevar name="domain" nojs="example.com" >}}/gotosocialinsecure_secretSome of the values presented in this guide can automatically be replaced with documentation variables.
{{< sitevar-preferences >}}
The following YAML configuration is an example Authelia client configuration for use with GoToSocial which will operate with the application example:
identity_providers:
oidc:
## The other portions of the mandatory OpenID Connect 1.0 configuration go here.
## See: https://www.authelia.com/c/oidc
clients:
- client_id: 'gotosocial'
client_name: 'GoToSocial'
client_secret: '$pbkdf2-sha512$310000$c8p78n7pUMln0jzvd4aK4Q$JNRBzwAo0ek5qKn50cFzzvE9RXV88h1wJn5KGiHrD0YKtZaR/nCb2CJPOsKaPK0hjf.9yHxzQGZziziccp6Yng' # The digest of 'insecure_secret'.
public: false
authorization_policy: 'two_factor'
require_pkce: false
pkce_challenge_method: ''
redirect_uris:
- 'https://gotosocial.{{< sitevar name="domain" nojs="example.com" >}}/auth/callback'
scopes:
- 'openid'
- 'profile'
- 'groups'
- 'email'
response_types:
- 'code'
grant_types:
- 'authorization_code'
access_token_signed_response_alg: 'none'
userinfo_signed_response_alg: 'none'
token_endpoint_auth_method: 'client_secret_basic'
{{% oidc-escape-hatch-claims-hydration client_id="gotosocial" claims="preferred_username" %}}
To configure GoToSocial there is one method, using the Configuration File.
oidc-enabled: true
oidc-idp-name: 'Authelia'
oidc-issuer: 'https://{{< sitevar name="subdomain-authelia" nojs="auth" >}}.{{< sitevar name="domain" nojs="example.com" >}}'
oidc-client-id: 'gotosocial'
oidc-client-secret: 'insecure_secret'
oidc-scopes:
- 'openid'
- 'email'
- 'profile'
- 'groups'
oidc-allowed-groups: []
oidc-admin-groups:
- 'admin'