Resolve common sign-in, SCIM, group sync, and user attribute issues in Appspace Cloud.
Start with the symptom that matches what you’re seeing in Microsoft Entra ID or Okta.
A user can’t sign in with SSO
- Appspace account — If you use SSO without SCIM or Just-in-Time (JIT) provisioning, the user must already exist in Appspace. Verify that their email address, first name, and last name match the identity provider. Confirm that they have the required Appspace permissions and licenses.
- Application assignment — If your identity provider requires app assignment, verify that the user or an applicable group is assigned to the Appspace application. A user provisioned through SCIM can still need an assignment to sign in.
- Entra ID SAML mappings — Confirm that Unique User Identifier uses user.mail, the given-name claim maps to firstname, and the surname claim maps to lastname.
- Okta SAML mappings — Verify the firstname, lastname, and email attribute statements.
The SSO test fails or sign-in stalls
Microsoft Entra ID
- Verify that the Identifier (Entity ID) is https://cloud.appspace.com.
- Verify that the Reply URL matches the Assertion URL shown in Appspace.
- Confirm that the current Entra Federation Metadata XML file is uploaded to Appspace.
- Run the SAML test again after correcting any settings.
Okta
- Verify that the Single sign-on URL matches the Assertion URL shown in Appspace.
- Verify that the Audience URI is https://cloud.appspace.com and the Name ID format is EmailAddress.
- Confirm that the Appspace Account Authentication page has the current Okta sign-on URL and X.509 signing certificate.
- Test again as a user assigned to the Appspace application in Okta.
SCIM users or groups are missing in Appspace
Microsoft Entra ID
After the initial provisioning cycle, Entra ID typically runs incremental syncs every 20–40 minutes. The first sync can take longer, especially when thousands of users are in scope.
- Confirm that provisioning is enabled and the intended users and groups are in scope. If provisioning is limited to assigned users and groups, verify their assignments to the Appspace enterprise application.
- If groups are missing, confirm that User Group Sync is enabled in Appspace.
- Use Provision on demand with one test user or a small test group.
- Refresh the Appspace Users page. If the test user or group still doesn’t appear, review the on-demand result and Entra provisioning logs.
Okta
Verify that the affected users are assigned to the Appspace application and that provisioning to Appspace is enabled. If a group is missing, check Push Groups in Okta and confirm that User Group Sync is enabled in Appspace.
The SCIM connection test fails
Compare the identity provider’s connection settings with the current SCIM values in Appspace.
Microsoft Entra ID
- Tenant URL — Use the SCIM Base URL from Appspace.
- Secret Token — Use the current Appspace bearer token.
Okta
- SCIM connector base URL — Use the URL shown in Appspace, such as https://cloud.appspace.com/identity/scim.
- Unique identifier field for users — Use email.
- Authentication Mode — Select HTTP Header.
- Authorization — Use the current Appspace bearer token.
Run the connection test again after confirming the values.
Okta can’t push a group again
If you deleted a pushed group directly in Appspace, Okta may still show it as linked. In the Appspace application’s Push Groups tab in Okta, unlink the existing group mapping, re-add the group, and retry the push.
Groups remain after User Group Sync is turned off
Turning off User Group Sync stops future synchronization. Groups that already exist in Appspace remain there. If a group is no longer needed, delete it manually in Appspace.
A custom user attribute is missing
- Confirm that the identity provider mapping uses the correct Appspace SCIM namespace.
- Verify that the mapped property name matches the corresponding Appspace user profile field.
- Test the mapping with one user and confirm the value appears in their Appspace profile before applying it more broadly.
Still having trouble?
Gather the identity provider name and relevant configuration, the affected user or group, the test results, and any sign-in or synchronization errors. Remove bearer tokens and other credentials from screenshots or logs before sharing them. Include these details when you submit an Appspace Support case.
Related guides

