---
title: Single sign-on and SCIM for Venom Cloud
description: Connect a Venom Cloud organisation to Okta, Microsoft Entra ID or Google Workspace over OIDC or SAML, and let SCIM keep the member list in step.
section: reference
order: 110
audience: [operator]
sources: [docs/cloud-sso.md, docs/cloud-mesh.md]
features: [reference.doc-cloud-sso]
---

For the owner of a Venom Cloud organisation who wants members to sign in through the company's identity provider (IdP) and the member list to follow the directory. Any IdP that speaks standard OpenID Connect or SAML 2.0 works; the console has step-by-step values for Okta, Google Workspace and Microsoft Entra ID.

Everything is in the console under Settings, Single sign-on. Owners change it; admins can look. Every change and every SCIM call goes into the audit log (`sso.*`, `scim.*`, `member.*`).

## Order of steps {#steps}

1. **Verify a domain.** Add your email domain. The page shows a TXT record: host `_venom-challenge.<domain>`, value `venom-domain-verification=<token>`. Add it at your DNS host and press Verify. The cloud makes one DNS lookup when you press it. A domain can belong to one organisation at a time, and only addresses in verified domains can sign in through your IdP.
2. **Connect the IdP.** Pick the IdP and protocol. The wizard shows the values to paste into the IdP and the fields to bring back.
3. **Test sign-in.** A test goes to the IdP and back and shows the email, name, groups and the role the person would get. It signs nobody in. A failure says why (wrong audience, clock skew, unsigned assertion).
4. **Enable.** Needs a test that passed on the current settings.
5. **Provisioning.** Just-in-time provisioning (on by default) makes a new person a member with the default role (developer unless changed). Group-to-role rules map IdP groups to roles; the first match wins and is applied at each sign-in. No rule, default or SCIM call ever creates, changes or removes an owner. A person already in the organisation with the same email is linked to their existing account.
6. **Require SSO** (optional). Members must come through the IdP. Owners keep their usual sign-in, so a broken IdP never locks the organisation out.
7. **SCIM** (optional, Okta and Entra). Create a SCIM token (shown once) and give the IdP the SCIM base URL and token. The IdP then creates, updates and deactivates members.

## URLs {#urls}

| What | URL |
|---|---|
| An organisation's sign-in link (app tiles, bookmarks) | `https://<cloud>/auth/sso/start?org=<org id>` |
| OIDC redirect URI | `https://<cloud>/auth/sso/oidc/callback` |
| SAML SP entity ID and metadata | `https://<cloud>/auth/sso/saml/<org id>` |
| SAML ACS URL | `https://<cloud>/auth/sso/saml/<org id>/acs` |
| SCIM base URL | `https://<cloud>/scim/v2` |

Sign-ins start at Venom. An IdP-initiated SAML response, one that answers no request, is refused; point app tiles at the sign-in link instead.

## Deprovisioning {#deprovisioning}

When SCIM sets a user inactive or deletes it:

- The member leaves the organisation; their console sessions end on the next page load.
- Their client keys follow the organisation's key policy: revoke (default), pause, or keep. Other cloud instances drop cached keys within 10 seconds.
- CLI logins they approved but that were not yet picked up are denied.
- Signing in through the IdP is refused while the SCIM user is inactive.
- Owners are never deprovisioned by SCIM (`409`); remove an owner in Settings, Members.

Reactivating the user makes them a member again with the role their groups map to. Revoked keys stay revoked; paused keys stay paused until resumed.

## Related

- [Glossary](/docs/reference/glossary.md)
- [Error codes](/docs/reference/errors.md)
