Seafile

Tested Versions

Before You Begin

You are required to utilize a unique client id and a unique and random client secret for all OpenID Connect relying parties. You should not use the client secret in this example, you should randomly generate one yourself. You may also choose to utilize a different client id, it’s completely up to you.

This example makes the following assumptions:

  • Application Root URL: https://seafile.example.com
  • Authelia Root URL: https://auth.example.com
  • Client ID: seafile
  • Client Secret: seafile_client_secret

Configuration

Application

To configure Seafile to utilize Authelia as an OpenID Connect Provider:

  1. Edit your Seafile seahub_settings.py configuration file and add configure the following:
ENABLE_OAUTH = True
OAUTH_ENABLE_INSECURE_TRANSPORT = False
OAUTH_CLIENT_ID = "seafile"
OAUTH_CLIENT_SECRET = "seafile_client_secret"
OAUTH_REDIRECT_URL = 'https://seafile.example.com/oauth/callback/'
OAUTH_PROVIDER_DOMAIN = 'auth.example.com'
OAUTH_AUTHORIZATION_URL = 'https://auth.example.com/api/oidc/authorization'
OAUTH_TOKEN_URL = 'https://auth.example.com/api/oidc/token'
OAUTH_USER_INFO_URL = 'https://auth.example.com/api/oidc/userinfo'
OAUTH_SCOPE = [
  "openid",
  "profile",
  "email",
  "groups",
]
OAUTH_ATTRIBUTE_MAP = {
    "id": (True, "preferred_username"),
    "name": (False, "name"),
    "email": (False, "email"),
}

Authelia

The following YAML configuration is an example Authelia client configuration for use with Seafile which will operate with the above example:

- id: seafile
  description: Seafile
  secret: seafile_client_secret
  public: false
  authorization_policy: two_factor
  redirect_uris:
    - https://seafile.example.com/oauth/callback/
  scopes:
    - openid
    - profile
    - email
  userinfo_signing_algorithm: none

See Also