Configuring SSO with ADFS
  • 04 Mar 2024
  • 3 Minutes to read
  • Dark
  • PDF

Configuring SSO with ADFS

  • Dark
  • PDF

Article Summary

Plan availability

Business and Enterprise Scale only


Web/Browser, Mac app, and Windows app 

Related reading

Setting up SSO for ADFS

The admin panel is a centralized tool to help Airtable admins manage their organization. Learn how to set up SSO logins for your organization.

Step 1: Adding a “Relying Party” using the ADFS setup wizard

  1. In the left navigation pane of ADFS, select Relying Party Trust, then Add Relying Party Trust, then Start.Picture1.png

  2. Click the radio button option to Enter data about the relying party manually, then click the Next button.Picture2.png

  3. You can enter whatever display name you want (like "Airtable") and any optional notes—then click the Next button again.Picture3.png

  4. Next, pick ADFS profile as the configuration profile.Picture4.png

  5. Click the Next button on the Configure Certificate page.


  6. For the Configure URL page, check the Enable support for the SAML 2.0 WebSSO protocol box and paste in this URL:


  7. For the Configure Identifiers page, add as a Relying party trust identifier.


  8. On the Configure Multi-factor Authentication Now? page, choose the "I do not want to configure multi-factor authentication settings for this relying party at this time." option.


  9. On the Choose Issuance Authorization Rules page, select the "Permit all users to access this relying party" option.


  10. On the final screen of the wizard, check the "Open the Edit Claim Rules dialog for this relying party trust when the wizard closes" box. This will open the Edit Claim Rules dialog once you click the Close button.


Step 2: Adding a “Claim Rule” in ADFS

  1. Once in the Edit Claim Rules dialog, go to the Issuance Transform Rules tab, then click the Add Rule button. This will open up the Add Transform Claim Rule Wizard.


  2. From within the Add Transform Claim Rule Wizard, you will be asked to Choose Rule Type. From the Claim rule template dropdown, select the Send LDAP Attributes as Claims option.


  3. Give your claim rule a name (like "LDAP Email") and map the E-Mail-Addresses LDAP attribute in the left column to the E-Mail Address outgoing claim type in the right column.


  4. You'll need to add another Transform Claim Rule here. This time, select the Transform an Incoming Claim option from the Claim rule template dropdown.


  5. Give this claim rule a name (like "Email Transform"), then set the following values:

    • Set Incoming claim type to E-Mail Address

    • Set Outgoing claim type to Name ID

    • Set Outgoing name ID format to Email

    • Select the Pass through all claim values radio button

  6. Airtable also supports the following additional attribute maps:

    • "urn:oid:" -> Basic Information; Last Name

    • "urn:oid:" -> Basic Information; First Name

  7. When you're done, click the OK button to save this Claim rule, and OK again to exit the Transform Claim Rule Wizard.

Step 3: Editing Airtable’s relying trust properties in ADFS

  1. Under the Advanced tab, select SHA-256 as the secure hash algorithm. Then, copy the following X.509 certificate and save it to something like airtable.crt:

    -----END CERTIFICATE-----
  2. Under the Signature tab, click Add, then upload airtable.crt. Click OK to complete. Next, you'll need to export your token signing certificate. In ADFS, click the Certificates folder, then Token Signing certificate.

  3. Click the Details tab, then click the Copy to File button.


  4. Next, export as a Base-64 encoded X.509 (.CER) file.


  5. After that, submit your sign on URL and x.509 certificate (you can open the .cer file in a text editor and copy-paste it in) following the steps in this article.

  6. After you have completed all of the steps, you should be able to log in from


If you encounter any issues or need additional assistance, please contact us. If there are any relevant ADFS logs (Control Panel -> Administrative Tools -> Event Viewer -> Applications and Services Logs -> AD FS -> Admin), please include them in your email.


If another team in my company already uses SSO with Airtable, how does this impact my Business or Enterprise Scale account?

In Airtable, our system expects Enterprise Scale accounts using shared domains—domains federated to multiple Enterprise accounts—to use the same SAML metadata for SSO. What this means is that if your company has existing Enterprise ScALE accounts with SSO configured, you will need to coordinate with the admins (or IT department) of the other accounts to obtain the current sign-in URLs, x.509 certificates, and ensure that your users have the necessary access to the Airtable tenant present in your company’s identity provider.

You can configure separate tenants or identity providers for domains unique to Enterprise Scale accounts, as each domain can be configured with its own SAML metadata.

Was this article helpful?