Table of Contents

Available with Enterprise

To ensure successful communication between your Identity Provider (IdP) and SeaTable Cloud as the Service Provider, the following technical and organizational requirements must be met.

Support for the SAML 2.0 Protocol

The IdP must support standard-compliant SAML 2.0, which SeaTable uses for authentication.

Ability to Create Applications and Use SeaTable-specific URLs

The IdP must allow the creation of applications and correctly configure and use the URLs provided by SeaTable Cloud for login, logout, and Assertion Consumer Service (ACS). Specifically, the URL for fetching the metadata XML must be directly accessible and must not redirect to another domain.

Transmission of Required SAML Attributes

At minimum, the following user attributes must be passed from the IdP to SeaTable:

  • contact_email (user’s email address)
  • name (user’s full name)
  • uid (unique user identifier that remains unchanged throughout the user’s lifecycle)

Validated SSL Certificate

The certificate provided by the IdP must be valid and trustworthy to ensure the integrity and security of authentication messages.

Access to Metadata

The IdP should provide metadata information (metadata URL) that can be stored in SeaTable.

Domain Ownership Verification

To assign SSO-enabled users to a SeaTable team, the email domain must be verified via a TXT record entered in the DNS.

Technical Ability to Create and Configure Applications

Your IdP must allow the creation of an application (connector) and its configuration to process authentication requests and assertions correctly.

Support for Signed Assertions

To enhance security, the IdP should issue signed SAML assertions and optionally allow SeaTable to sign authentication requests.

The following identity providers have already been successfully tested with SeaTable Cloud: