Seafile

Tested Versions

Before You Begin

Common Notes

  1. You are required to utilize a unique client id for every client.
  2. The client id on this page is merely an example and you can theoretically use any alphanumeric string.
  3. You should not use the client secret in this example, We strongly recommend reading the Generating Client Secrets guide instead.

Assumptions

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 1.0 Provider:

  1. Seafile may require some dependencies such as requests_oauthlib to be manually installed. See the Seafile documentation in the see also section for more information.

  2. 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",
]
OAUTH_ATTRIBUTE_MAP = {
    "email": (True, "email"),
    "name": (False, "name"),
    "id": (False, "not used"),
}

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: '$plaintext$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