Skip to content

SSO (SAML) and SCIM

Single sign-on lets people sign in to NamiDB Cloud with your identity provider (IdP), join your organization automatically, and lose access when you deprovision them. It is available on Scale and Enterprise.

Everything lives under Settings → Single sign-on (owners and admins).

Connect your identity provider

  1. Create a SAML app in your IdP (Okta, Microsoft Entra ID, Google Workspace, OneLogin, JumpCloud, …). Copy the ACS URL, entity ID and, if your IdP imports it, the SP metadata URL from the Identity provider section of the Single sign-on page. Make sure the app sends the user’s email address.

  2. Give NamiDB the IdP’s metadata: its metadata URL (https) or the metadata XML pasted in. Saving again later refreshes it, for example after the IdP rotates its signing certificate.

  3. Verify your domains. Add each email domain (acme.com) and publish the TXT record the page shows:

    _namidb-verification.acme.com. TXT "namidb-verification=<token>"

    Then press Verify. A domain can belong to one organization only, and only addresses in verified domains can use SSO, join through it or be provisioned.

  4. Choose the sign-in rules (Sign-in and roles): the default role for people who join through SSO, and optionally a role attribute and mappings.

Signing in

People sign in at app.namidb.com/login/sso (or Sign in with SSO on the login page) by entering their work address. NamiDB finds your IdP from the domain and sends them there.

New SSO users accept the Terms like everyone else, the first time.

Just-in-time membership and roles

The first SSO sign-in of a person in a verified domain adds them to the organization with the default role. To set roles from the IdP instead, name the role attribute (usually groups) and add one mapping per line:

Engineering = developer
Finance = billing
Platform Admins = admin

When several values match, the most privileged role wins. The mapping is applied again at every sign-in, so changing someone’s groups in the IdP changes their role in NamiDB. SSO never grants or changes the owner role, and never changes an owner.

Requiring SSO

Turn on Require SSO to make members whose address is in a verified domain reach the organization only through your IdP. Their password, magic-link and social sign-ins still open their account, but not this organization: the console sends them to SSO.

  • You can only turn it on from an SSO session, so you can’t lock yourself out.
  • Management tokens created by someone the requirement keeps out stop working (403 token_inactive), and exports check it too.
  • Members outside your verified domains (contractors, for example) are not affected.
  • If the organization leaves Scale, SSO, SCIM and the requirement switch off; the configuration is kept for when you come back.

SCIM provisioning

SCIM 2.0 lets your IdP create, update and deactivate members.

Base URLhttps://app.namidb.com/api/scim/v2
AuthenticationBearer token nmdb_scim_…
ResourcesUsers, Groups, plus ServiceProviderConfig, ResourceTypes, Schemas
Filterseq on userName, externalId and emails.value
PATCHAs Okta and Microsoft Entra ID send it

Create tokens in the SCIM provisioning section (shown once; up to 5 active per organization), and paste the base URL and token into your IdP’s provisioning settings.

  • Groups are roles: admin, developer, billing, member, viewer. Names like “NamiDB Developers” map to the role they contain.
  • A provisioned person is linked to their SSO account now, or at their first SSO sign-in.
  • Deactivating or deleting a person in the IdP removes their membership and signs them out of every session. They can’t come back through just-in-time sign-in until the IdP reactivates them.
  • Owners are never removed through SCIM (409, owner_protected): only an owner removes an owner.
  • Every SCIM change is in the audit log with the actor “SCIM”.

Troubleshooting

SymptomCheck
SSO sign-in doesn’t find your IdPThe address’s domain is verified, and the IdP is connected and the plan is Scale or Enterprise
Signed in, but not in the organizationThe address is in a verified domain; the IdP sends the email address; SCIM didn’t deactivate the person
Wrong roleThe role attribute’s name and values exactly match your mapping lines
Domain won’t verifyThe TXT record is on _namidb-verification.<domain> and has propagated (dig TXT _namidb-verification.acme.com)

Still stuck? Open a ticket with the category Account & access: see Support.