website/integrations/chat-communication-collaboration/seatable/index.md
SeaTable is a no-code database and app builder platform that provides a web-based, spreadsheet-like interface for organizing data, building apps, and automating workflows. It is designed to function as a collaborative database with features like tables, views, forms, and permissions.
The following placeholders are used in this guide:
seatable.company is the FQDN of the SeaTable installation.authentik.company is the FQDN of the authentik installation.:::info SaaS vs Selfhosted SeaTable is available as both a cloud SaaS and a self-hosted solution. This guide is for self-hosters only. :::
:::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. :::
To support the integration of SeaTable with authentik, you need to create an application/provider pair in authentik.
Log in to authentik as an administrator and open the authentik Admin interface.
Navigate to Applications > Applications and click Create with Provider to create an application and provider pair. (Alternatively you can first create a provider separately, then create the application and connect it with the provider.)
https://seatable.company/sso/.https://seatable.company/saml/acs/.https://seatable.company.Post.https://seatable.company/saml/metadata/.Click Submit to save the new application and provider.
To support the integration of authentik with SeaTable you need to configure certificates and then enable SAML authentication.
SeaTable requires the signing certificate from authentik and its own signing certificate. Follow these steps to configure the required certificates on your SeaTable deployment:
/opt/seatable-server/certs directory and navigate to it.idp.crt.openssl req -x509 -nodes -days 3650 -newkey rsa:2048 -keyout sp.key -out sp.crt
After completing these steps, the /opt/seatable-server/certs directory should contain: idp.crt, sp.crt, and sp.key.
authentik's metadata download URL returns a 302 redirect but SeaTable requires the effective URL. Run the following command to determine the effective URL:
curl -Ls -o /dev/null -w '%{url_effective}\n' "<metadata_download_URL>" 2>/dev/null
The output of this command will be required as the SAML_REMOTE_METADATA_URL in the next section.
Add the following block to your SeaTable configuration file:
ENABLE_SAML = True
SAML_PROVIDER_IDENTIFIER = 'authentik'
SAML_REMOTE_METADATA_URL = '<metadata_effective_url>'
SAML_ATTRIBUTE_MAP = {
'http://schemas.goauthentik.io/2021/02/saml/uid': 'uid',
'http://schemas.xmlsoap.org/ws/2005/05/identity/claims/emailaddress': 'contact_email',
'http://schemas.xmlsoap.org/ws/2005/05/identity/claims/name': 'name',
}
SAML_CERTS_DIR = '/shared/certs'
Restart the SeaTable service or Docker container to apply the changes.
To confirm that authentik is integrated correctly with SeaTable, log out, then navigate to the SeaTable login page, then click Single Sign-On. You should be redirected to authentik to log in, and if successful, redirected to SeaTable.
:::info Troubleshooting
Check opt/seatable-server/seatable/logs/dtable_web.log for troubleshooting info if authentication fails.
:::