Skip to Content
Onshore is in early access. Don’t load real customer data until the items in Known limits are closed.
Sign-in and identityOverview

Sign-in and identity

Every sign-in to the console needs two factors. How the first is checked, and how accounts are managed, is up to you:

MethodFirst factorSecond factorAccountsEdition
PasswordOnshore passwordAuthenticator code or passkeyAdded by an adminAll
Single sign-onYour identity provider (SAML 2.0 or OIDC)Your identity provider’s MFAAdded by an admin, or created on first sign-inEnterprise, Cloud
SCIMUsually with single sign-onYour identity providerCreated, updated and removed by your identity providerEnterprise, Cloud
LDAPYour directory’s passwordAuthenticator code or passkeyAdded by an admin, or created on first sign-inEnterprise, Cloud

All are set up in Settings → Sign-in.

Settings, Sign-in, for an Enterprise install: two-factor, single sign-on, groups and roles, directory sync and LDAP

Safety rules that always apply

  • The last admin is never removed by an identity provider: if a change would leave no active admin, the admin role is kept.
  • Local accounts keep their password. An admin added by hand (a break-glass account) can always sign in with their own password and code, unless you turn passwords off.
  • Every sign-in and account change is in the audit log, with how it happened (password, single sign-on, LDAP, SCIM), and sends an identity.changed webhook where relevant.
Last updated on