Identity and people
Test and roll out SSO
Check a pilot account, invitations, recovery and offboarding before a wider rollout.
Run a small pilot after your Diakrin onboarding contact confirms activation. Keep your recovery owner available throughout the pilot.
Pilot checklist
- Use a fresh browser session. Open the console, choose Sign in with company SSO, and enter an assigned pilot user’s work email.
- Confirm that the expected company identity provider opens. Complete sign-in and MFA when required by your identity policy.
- Confirm return to the correct Diakrin console, then accept the pilot user’s organization invitation. Reload and verify that the organization remains available.
- Assign the member only the pilot project. Confirm the member can open that project and cannot view unrelated projects or another organization’s resources.
- Test an unassigned identity-provider user. Check that application assignment prevents the new sign-in, where your provider supports that policy.
- Test an authenticated user who has no Diakrin invitation or membership. Signing in must not grant access to your organization.
- Remove the pilot member in Diakrin and retry their previous project and coding-tool connection. Access should be denied by current organization/project authorization.
- Sign out, sign in again and test recovery with the second owner before expanding the provider assignment.
Record the date, provider, environment, pilot accounts, expected access and actual results. An identity-provider test button alone does not verify the return to Diakrin or project authorization.
Existing account migration
SSO may create a different Diakrin identity from a previous password or social-login account with the same email. Existing permissions are not automatically transferred by email matching.
- Keep the existing owner signed in in a separate browser profile.
- Sign in through SSO in a fresh profile and accept an authorized invitation for that identity.
- Have an existing owner confirm the new member, set the intended role and assign projects. If ownership must move, promote the new identity to Owner explicitly.
- Verify project access, ownership, reload and coding-tool reconnection using SSO before removing old memberships.
- Keep at least one verified owner. Do not delete the old authentication account as a shortcut to linking identities.
Broader rollout
Share the console sign-in URL and invitation instructions with your team after the pilot passes. Expand the identity-provider assignment in stages. Explain that employees join through an invitation and that Member access requires a project assignment.
Enforcing SSO for every console session is not available. If your company requires it, resolve that requirement with Diakrin before rollout; assigning an SSO application does not enforce it on alternate sign-in methods. Company apps can require SSO through the sign-in floor. To automate joiners and leavers, add SCIM provisioning after the pilot.
Certificate renewal and offboarding
Tell your Diakrin onboarding contact before rotating a signing certificate or changing metadata. Agree a change window, update the existing connection and retest the pilot. Changing the IdP Entity ID can create a new identity boundary and requires a migration review.
When an employee leaves, remove their Diakrin organization membership and app grants as well as their identity-provider assignment. With SCIM provisioning, deactivating the person in your identity provider removes their membership for you. IdP disablement can block future sign-ins while an existing session remains valid. Do not rely on it for immediate Diakrin revocation.
Diakrin sign-out does not guarantee logout from your identity provider or every company application. See Manage access and security.