SSO is a feature only available for Airtable Enterprise payment plans. If you are interested in inquiring about enterprise pricing, you can contact us here.
This article is intended for administrators setting up SSO for their teams.
- If you are looking for information on setting up SSO with Okta, please read this article instead.
- If you are looking for information on setting up SSO with Google, please read this article instead.
If you use an identity provider other than Google or Okta and wish to configure SSO for your organization, you will need to fill out this form. You will need your sign on URL, x.509 Certificate, and your IdP metadata file.
Setting up SSO for ADFS
In the left navigation pane of ADFS, select Relying Party Trust, then Add Relying Party Trust, then Start.
Click the radio button option to Enter data about the relying party manually, then click the Next button.
You can enter whatever display name you want (like "Airtable") and any optional notes—then click the Next button again.
Next, pick AD FS profile as the configuration profile.
Click the Next button on the Configure Certificate page.
For the Configure URL page, check the Enable support for the SAML 2.0 WebSSO protocol box and paste in this URL: https://airtable.com/auth/ssoCallback
For the Configure Identifiers page, add https://airtable.com/sso/metadata0418.xml as a Relying party trust identifier.
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.
On the Choose Issuance Authorization Rules page, select the "Permit all users to access this relying party" option.
On the final screen, 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.
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.
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.
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.
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.
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
Airtable also supports the following additional attribute maps:
- "urn:oid:126.96.36.199" -> Basic Information; Last Name
- "urn:oid:188.8.131.52" -> Basic Information; First Name
When you're done, click the OK button to save this Claim rule, and OK again to exit the Transform Claim Rule Wizard.
Next, you'll need to edit Airtable's relying trust properties. 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:
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.
Click the Details tab, then click the Copy to File button.
Next, export as a Base-64 encoded X.509 (.CER) file.
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) at https://airtable.com/shrKtuQMVEEyTw4cS.
After you have completed these steps and we have confirmed receipt of the information from the previous step, you should be able to log in from https://airtable.com/sso/login.
If you encounter any issues or need additional assistance, please email [email protected]. 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.