SAML setup

NameDrop supports SAML 2.0 with all major identity providers. The setup is currently driven by NameDrop’s support team alongside your IdP admin during Corporate Plan rollout.

Already onboarding?

There’s a detailed setup guide with the exact values and per-IdP walkthroughs (Google Workspace, Azure AD, ADFS). It requires an access code, which we share during onboarding — email hello@namedrop.io if you need it.

High-level flow

1. Tell us your IdP — Okta, Azure AD, Google Workspace, OneLogin, JumpCloud, ADFS, or any standard SAML 2.0 IdP.
2. NameDrop generates the SP metadata — Entity ID, ACS URL, and SP certificate, all hosted at a per-tenant URL we share.
3. You register NameDrop in your IdP — paste our SP metadata into your IdP’s app catalog as a custom SAML app.
4. You send us your IdP metadata — Entity ID, SSO URL, and the IdP signing certificate.
5. Attribute mapping — map email, firstName, lastName (minimum) to NameDrop’s SAML attribute names.
6. Test the flow — NameDrop runs a test login against your IdP; you confirm the attributes flow through.
7. Go live — NameDrop enables SAML enforcement on your tenant. Users hit your IdP for login from that point forward.

Where users start their sign-in

NameDrop supports both SAML initiation models:

• SP-initiated (default) — users start at NameDrop and are redirected to your IdP to authenticate. Works as soon as your connection is live, and is the more secure of the two because NameDrop can verify the response matches the request it sent.
• IdP-initiated — users start at your IdP: an app tile, intranet bookmark, or portal launcher. Available on request; it needs a one-time switch on our side plus a specific RelayState value in your IdP.

Most customers use SP-initiated only. Choose IdP-initiated if your users expect to launch NameDrop from a company portal. The detailed setup guide covers both.

Required attributes

NameDrop expects	Standard SAML name
email	urn:oid:0.9.2342.19200300.100.1.3 (mail)
firstName	urn:oid:2.5.4.42 (givenName)
lastName	urn:oid:2.5.4.4 (sn)

Optional attributes (like department, title) can be passed through if you want them surfaced in NameDrop’s directory.

What about SCIM / auto-provisioning?

SCIM-based provisioning isn’t available yet — NameDrop relies on email domain auto-detection: users who sign in via SSO whose email matches your org domain get auto-assigned to your tenant.

Get started

Setup is a single short call with our team plus the IdP metadata exchange. Email hello@namedrop.io with your IdP name to kick things off.