Google Workspace SSO + SCIM
For tenants using Google Workspace as their primary IdP. Total time: 10 minutes.
Part 1 — SAML SSO
Section titled “Part 1 — SAML SSO”-
In Claresia Onboarding Portal, click Configure SSO (Step 4). Choose the Google Workspace tab. Copy the ACS URL + Audience URI.
-
In Google Admin Console (admin.google.com), go to Apps → Web and mobile apps → Add app → Add custom SAML app.
- App name:
Claresia - App icon: upload from
docs.claresia.com/brand/claresia-mark.svg
- App name:
-
On the Google Identity Provider details page, download the IdP metadata (XML). Keep handy.
-
Service provider details:
- ACS URL: paste from portal
- Entity ID: paste Audience URI from portal
- Name ID format:
EMAIL - Name ID:
Basic Information > Primary email
-
Attribute mapping:
Google Directory attribute App attribute Primary emailemailFirst namefirstNameLast namelastNameDepartment(optional)department -
Group membership (Optional but recommended):
- Add a group filter:
claresia-*→ mapped togroupsattribute.
- Add a group filter:
-
Click Finish. On the next page, enable the app for your Org Unit (or for everyone).
-
Back in Claresia Onboarding Portal, upload the IdP metadata XML you downloaded in Step 3 → click Test login → authenticate as a Google Workspace user → green check.
Part 2 — SCIM provisioning (via Google Cloud Identity)
Section titled “Part 2 — SCIM provisioning (via Google Cloud Identity)”Google Workspace uses Google Cloud Identity for SCIM. Premium edition (or Cloud Identity Premium) is required for SCIM endpoints.
-
In Claresia Onboarding Portal, copy the SCIM endpoint URL + bearer.
-
In Google Admin Console, open Apps → Web and mobile apps → Claresia → Auto-provisioning → Configure.
-
Authorization Method: Bearer Token → paste the bearer.
-
Endpoint URL: paste the SCIM endpoint URL.
-
Verify connection — should return success.
-
Attribute mapping:
Primary email→userNameFirst name→name.givenNameLast name→name.familyName- Add
Groups→groups
-
Provisioning scope: choose the Org Units to provision (your
claresia-*groups +claresia-users). -
Activate. Initial sync runs within 5 minutes.
-
Back in portal, click Sync now to force an immediate pull. User counts should update within 60 seconds.
Part 3 — Group → role mapping
Section titled “Part 3 — Group → role mapping”| Google group | Claresia role |
|---|---|
claresia-admins@yourcompany.com | tenant_admin |
claresia-auditors@yourcompany.com | auditor |
claresia-users@yourcompany.com | member |
Group emails must be created in Google Groups first
(groups.google.com/a/yourcompany.com).
De-provisioning behavior
Section titled “De-provisioning behavior”When a user is suspended in Google Admin (or removed from all claresia-*
groups), Google Cloud Identity sends a SCIM PATCH within 5 minutes (forcible
sync via Claresia portal cuts this to <60s). Claresia revokes the JWT and
removes skill entitlements immediately.
Common gotchas
Section titled “Common gotchas”| Symptom | Cause | Fix |
|---|---|---|
| SCIM “Provisioning is paused” | Token expired or rotated | Re-generate from portal, re-enable in Google Admin |
| Users provisioned but no groups | Group scope not enabled | Add Groups to SCIM scope in Step 6 |
Test login returns “Email not provisioned” | User not in any claresia-* group | Add them, wait 5 min, retry |