Administration

Rolling out single sign-on and SCIM: a checklist

The order to do things in when you connect AccordSeal to your identity provider, so that nobody is locked out and leavers lose access immediately.

By the AccordSeal team · Updated · 5 min read

Single sign-on puts your identity provider in charge of who can open AccordSeal. SCIM goes a step further and creates, updates and deactivates accounts automatically. Done in the right order, the rollout is uneventful.

Single sign-on needs the sso entitlement on your plan, and the person setting it up needs the sso.manage permission.

1. Verify your email domain

Add the DNS TXT record AccordSeal gives you. A domain can belong to one organization only. Verification is what allows home-realm discovery: when someone types their work email on the login page, they are sent to your identity provider.

2. Create the connection

Choose the protocol your identity provider supports:

  • SAML 2.0 — SP-initiated sign-in, with IdP-initiated sign-in as an option. Each connection has its own service-provider metadata and key pair. Responses must be signed, and a replay cache rejects a response that is presented twice.
  • OpenID Connect — any provider that supports issuer discovery.

3. Map groups to roles

With just-in-time provisioning, a person's account is created the first time they sign in, and their identity-provider groups decide their role. Group mapping can grant Admin, Member or Viewer. It never grants Owner; that stays a deliberate, manual decision.

4. Test with a pilot group

Ask three or four people to sign in through the identity provider. Check that each lands in the right role and department. Do this before the next step.

5. Turn on “Require single sign-on”

Enforcement revokes existing sessions that were not created through SSO, so people will be asked to sign in again. Tell them beforehand.

Owners keep a break-glass password. This is intentional: if your identity provider has an outage or a certificate expires, an owner can still get in and fix the connection. Store that password as carefully as any other emergency credential.

6. Connect SCIM

Generate an organization-scoped SCIM token and add AccordSeal as a provisioning target. Users and Groups are supported, and both the Okta and the Microsoft Entra styles of PATCH request work.

The important behaviour is deactivation: when your identity provider deactivates a user, AccordSeal suspends the member and revokes their sessions. A leaver loses access at once, not at their next sign-in.

Things to know

  • SAML single logout is supported. Signing out of your identity provider also ends the AccordSeal session, and SCIM deactivation revokes sessions at once.

Run your next agreement from draft to proof.

Start with the Free plan, or ask us to walk your team through AccordSeal with your own documents.