Leaving Airtable? Bring your bases to Artavolo, checked record by record. See how

Set up single sign-on (OpenID Connect)

Updated

With single sign-on, people sign in to Artavolo with the accounts they already have in your organisation, and when someone leaves your directory they lose access to Artavolo with everything else. It works with any provider that speaks OpenID Connect, such as Microsoft Entra ID, Okta, Keycloak and Google Workspace.

Register Artavolo with your provider

  1. In your identity provider, create a web application that uses OpenID Connect.
  2. Choose a short key for the provider, such as entra, and allow this redirect address: https://<your host>/auth/sso/<key>/callback.
  3. Note the provider's discovery address, the client id and the client secret. With Entra ID, also add the email optional claim to the ID token.

Add the provider in Artavolo

  1. Sign in as an administrator, choose Control panel in the account menu, then Settings, Single sign-on.
  2. Under Identity providers, add one entry per provider with its key, name, discovery address, client id and client secret.
  3. Press Save providers. Client secrets are encrypted when saved and never shown again; leave the secret empty later to keep the stored one.
  4. Press Test discovery to check that the provider answers.
  5. Tick Enable single sign-on.

Decide how people get accounts

  • Link an identity to an existing account with the same verified e-mail matches someone's first sign-in to the account they already had.
  • Create accounts on first sign-in (just-in-time) makes an account the first time someone arrives, and puts them in the workspace you name under Workspace for new accounts (id) with the Role in that workspace you choose. Leave the workspace at 0 to give each person a workspace of their own.
  • E-mail domain → provider map (JSON) sends each e-mail domain to the right provider when you have more than one, for example {"acme.de":"entra"}.

Make it the only way in

Tick Enforce: password login only for administrators and everyone else must sign in through the provider, so there are no other passwords left to leak. Sign-in codes by e-mail are switched off too. Keep at least one administrator who can sign in with a password, in case the provider is unavailable.

Good to know

  • Single sign-on is part of Enterprise on your own server, and needs a licence key that includes it. You can prepare the settings before the key is in place. See Apply a licence key.
  • Every sign-in, failed sign-in and account creation is in the audit log, with the method used.
  • Removing someone from a workspace ends their access at once, including through their API tokens and AI chat.
  • People who sign in through single sign-on and delete their own account confirm with their e-mail address, not a password.
  • SAML 2.0 and LDAP or Active Directory are not set up on this screen; ask us if you need them.
  • The single sign-on guide has the steps for Entra ID, Keycloak and Okta.

Related