Account / SSO and SCIM
SSO and SCIM
Scale workspaces authenticate through your identity provider and can provision members from your directory.
SAML single sign-on
Tested with Okta, Entra ID, Google Workspace, JumpCloud and OneLogin. Any SAML 2.0 provider works.
- In Workspace settings → Authentication, copy the ACS URL and entity ID.
- Create the application in your identity provider and map
email,firstNameandlastName. - Paste the provider metadata URL back into Dicast and verify with a test sign-in.
- Once verified, enable Require SSO. Existing sessions are not terminated; the next sign-in goes through your provider.
Members then sign in at your-workspace.dicast.dev rather than through a Git provider.
SSO and Git identity
SSO governs who can reach the dashboard. Reviews still run under the app installation on your Git host, so revoking someone in your identity provider removes their Dicast access but does not remove their repository access — that remains your Git host’s job.
SCIM provisioning
SCIM 2.0 is available once SSO is verified. Generate a token in the same settings screen and point your provider at https://api.dicast.dev/scim/v2.
| Operation | Effect in Dicast |
|---|---|
| User created | Member added; a seat is consumed only once they open a reviewed pull request. |
| User deactivated | Access revoked at the next request; sessions invalidated within five minutes. |
| Group pushed | Mapped to a Dicast role — admin, member, or read-only. |