6ed5cb5249
* website/integrations: rename "Create with Provider" to "New Application" The application list page now uses a split-button labeled "New Application" instead of the old "Create with Provider" dropdown. Update all 113 integration guides to match. * website/docs: update flow, stage, and policy button labels - "Create" → "New Flow", "New Stage", "New Policy" for trigger buttons - "Finish" → "Create Flow", "Create Stage", "Create Policy" for submit - "Create and bind stage" → "New Stage" / "Bind Existing Stage" - "Create" (binding submit) → "Create Stage Binding" * website/docs: update provider button labels - "Create" → "New Provider" for trigger buttons - "Create with Provider" → "New Application" in RAC docs - "Create" → "New Property Mapping", "New RAC Endpoint", "New Prompt" for related entity creation * website/docs: update directory button labels - "Create" → "New Source" for federation/social login pages - "Create" → "New Role", submit → "Create Role" - "Create" → "New Invitation" - Policy binding submit → "Create Policy Binding" * website/docs: update endpoint device and system management button labels - "Create" → "New Endpoint Connector", "New Enrollment Token", "New Device Access Group", "New Flow" - Submit → "Create Device Access Group" - "Create" → "New Notification Rule", "New Notification Transport" - Binding submit → "Create Policy Binding" * Reorganize policy documentation * website/docs: address policy docs review feedback * post-rebase * website/docs: Reorganize policy documentation -- Revisions (#21601) * apply suggestions * Fix escaped. * Fix whitespace. * Update button label. * Fix phrasing. * Fix phrasing. * Clean up stragglers. * Format. --------- Co-authored-by: Dominic R <dominic@sdko.org>
4.3 KiB
title, sidebar_label, support_level
| title | sidebar_label | support_level |
|---|---|---|
| Integrate with Seafile | Seafile | community |
What is Seafile
Seafile is an open-source, cross-platform file-hosting software system. Files are stored on a central server and can be synchronized with personal computers and mobile devices through apps. Files on the Seafile server can also be accessed directly via the server's web interface. -- https://seafile.com
Preparation
The following placeholders are used in this guide:
seafile.companyis the FQDN of the Seafile installation.authentik.companyis the FQDN of the authentik installation.
:::info This documentation lists only the settings that you need to change from their default values. Be aware that any changes other than those explicitly mentioned in this guide could cause issues accessing your application. :::
authentik configuration
To support the integration of Seafile with authentik, you need to create an application/provider pair in authentik.
Create an application and provider in authentik
-
Log in to authentik as an administrator and open the authentik Admin interface.
-
Navigate to Applications > Applications and click New Application to open the application wizard.
- Application: provide a descriptive name, an optional group for the type of application, the policy engine mode, and optional UI settings.
- Choose a Provider type: select OAuth2/OpenID Connect as the provider type.
- Configure the Provider: provide a name (or accept the auto-provided name), the authorization flow to use for this provider, and the following required configurations.
- Note the Client ID and Client Secret values because they will be required later.
- Set a
Strictredirect URI tohttps://seafile.company/oauth/callback/.
- Configure Bindings (optional): you can create a binding (policy, group, or user) to manage the listing and access to applications on a user's My applications page.
-
Click Submit to save the new application and provider.
Seafile configuration
To support the integration of Seafile with authentik, you'll need to update the seahub_settings.py file of your Seafile deployment (the location may vary depending on your installation and deployment methods):
CSRF_TRUSTED_ORIGINS = ['https://seafile.company']
ENABLE_OAUTH = True
# Automatically creates a user in Seafile when they log in for the first time. Defaults to True.
OAUTH_CREATE_UNKNOWN_USER = True
# Automatically activate Seafile users when they log in for the first time. Defaults to True.
OAUTH_ACTIVATE_USER_AFTER_CREATION = True
OAUTH_CLIENT_ID = '<client_id>'
OAUTH_CLIENT_SECRET = '<client_secret>'
OAUTH_REDIRECT_URL = 'https://seafile.company/oauth/callback/'
OAUTH_PROVIDER = 'authentik'
OAUTH_PROVIDER_DOMAIN = 'https://authentik.company'
OAUTH_AUTHORIZATION_URL = 'https://authentik.company/application/o/authorize/'
OAUTH_TOKEN_URL = 'https://authentik.company/application/o/token/'
OAUTH_USER_INFO_URL = 'https://authentik.company/application/o/userinfo/'
OAUTH_SCOPE = ["openid", "profile", "email"]
OAUTH_ATTRIBUTE_MAP = {
"email": (True, "contact_email"),
"name": (False, "name"),
"sub": (False, "uid"),
}
# Optionally set the following variable to automatically redirect users to the login page
LOGIN_URL = 'https://seafile.company/oauth/login/'
# Enable client to open an external browser for single sign on
# When it is false, the old builtin browser is opened for single sign on
# When it is true, the default browser of the operation system is opened
# The benefit of using system browser is that it can support hardware 2FA
# Since 11.0.0, and sync client 9.0.5, drive client 3.0.8
CLIENT_SSO_VIA_LOCAL_BROWSER = True # default is False
Configuration verification
To confirm that authentik is properly configured with Seafile, log out of Seafile. Then, navigate to the Seafile login page, and click Log in using SSO. You should be redirected to authentik to log in, and if the process is successful, you'll be taken to the Seafile dashboard.