Enterprise identity

Enterprise SSO admin guide.

Configure Cognito-backed SAML or OIDC for governed agent planning with explicit domain ownership, callback and logout URLs, claims mapping, workspace role assignment, testing evidence, troubleshooting, and rollback steps before broad customer invites.

SSO assumptions

SAML, OIDC, and Cognito-only launches must name the accepted identity posture.

The enterprise packet should say which mode is active, who accepted it, and which Linear blocker tracks any remaining SSO limitation.

Cognito-backed SAML

Enterprise SAML federation terminates at Cognito and maps assertions into the workspace role model before the custom app session is issued.

Customer provides

  • IdP metadata URL or signed metadata XML.
  • Entity ID, SSO URL, signing certificate, and NameID format.
  • Group or app-role claim names that can drive role assignment.

Cognito-backed OIDC

Enterprise OIDC federation uses Cognito as the relying party, validates issuer metadata, and converts ID token claims into workspace membership fields.

Customer provides

  • Issuer URL, client ID, client secret handoff path, and JWKS availability.
  • Allowed scopes such as openid, email, profile, and groups.
  • Claim names for subject, email, display name, and group membership.

Cognito-only fallback

If enterprise SSO is not enabled for launch, the customer explicitly accepts Cognito email auth as a temporary limitation with a dated follow-up.

Customer provides

  • Named approver for the SSO limitation.
  • Accepted MFA and invite workflow for launch users.
  • Target date or blocker issue for SAML/OIDC enablement.

Admin setup

Cognito federation, custom domains, callback URLs, claims, roles, and sessions all need separate rollback notes.

AreaAdmin actionRequired evidenceRollback
Cognito federationCreate the SAML or OIDC identity provider in Cognito, bind it to the app client, and keep provider secrets outside source control and Terraform state outputs.Provider type, issuer/entity ID, metadata source, certificate expiry, and app client binding.Disable the provider on the app client and return affected users to the accepted Cognito-only invite path.
Custom domainConfirm the Cognito hosted auth domain or customer-facing auth subdomain, certificate, DNS ownership, and environment separation.Domain, certificate status, DNS validation, environment, and owner approval.Restore the previous hosted UI domain or remove the customer domain from the launch allowlist.
Callback and logout URLsAllowlist exact callback and logout URLs for dev, staging, preview, and production before inviting customer users.URL matrix covering login callback, logout return, app redirect, and blocked external redirect checks.Revert Cognito app client callback/logout URLs to the last known good matrix.
Claims mappingMap subject, email, display name, groups, workspace role, and billing admin claims into normalized workspace membership fields.Claim table, sample redacted assertion or ID token, and validation result for every launch role.Return unmapped users to read-only or disable SSO login until the role mapping is corrected.
Role assignmentAssign least-privilege workspace roles from IdP groups and require human approval for owner, admin, billing-admin, and agent roles.Role mapping table, approver, backup admin, and emergency stop owner.Remove the role mapping group or demote affected users to read-only while the customer owner reviews access.
Session securityConfirm MFA posture, token lifetime, session cookie settings, account recovery path, and audit events for login, logout, and role changes.MFA decision, token/session lifetime, recovery owner, and audit smoke result.Shorten session lifetime, revoke sessions, and pause invites until recovery and audit checks are healthy.

Claims and role mapping

Role assignment fails closed when groups, workspace roles, or billing claims are unknown.

Source claimTarget fieldValidation
sub, NameID, or persistent identifierexternalSubjectIdStable across logins and never reused for another person in the customer tenant.
emailemailVerified, lowercased, customer-owned domain unless an explicit guest exception exists.
name, given_name, family_namedisplayNameSafe for UI display and not used for authorization decisions.
groups or memberOfexternalGroupsGroup values are normalized and reviewed before they grant workspace roles.
buildr_plannr_role or group mappingworkspaceRoleOnly allowed workspace roles are accepted; unknown roles fail closed.
billing_admin or finance groupbillingAccessBilling access is granted only to approved finance or workspace owner groups.

Testing and troubleshooting

Test login, callback, logout, claims, roles, and admin references before inviting broad customer users.

Validate IdP metadata and Cognito provider status

Auth owner: Provider ID, issuer/entity ID, certificate expiry, and app client binding.

Run login, callback, app redirect, and logout smoke tests

QA owner: Browser evidence for /login, callback return, /app, logout, and denied external redirects.

Verify claims and role assignment with test users

Security owner: Redacted token/assertion sample, expected role, actual role, and audit event.

Review admin surfaces before broad invites

Workspace admin: Workspace settings, admin diagnostics, support path, and emergency owner confirmation.

Rollback steps

  1. Pause broad customer invites

    Launch owner: Linear blocker, customer notification draft, and invite freeze timestamp.

  2. Disable or detach the failing Cognito identity provider

    Auth owner: Provider/app client change, previous config reference, and rollback approver.

  3. Revoke affected sessions and reset fallback access

    Security owner: Session revocation note, impacted users, and recovery path.

  4. Restore the last known good callback/logout URL matrix

    Infra owner: Environment, domain, callback URL, logout URL, and DNS status.

Need help?

SSO support starts from provider, URL, claim, role, session, and audit evidence, not screenshots with tokens or private customer data.

Include the Linear blocker, environment, provider type, callback/logout URL matrix, redacted claim sample, expected role, actual role, and rollback owner.

Open SSO support