Integration & SSO Issues

Find step-by-step solutions for SAML Single Sign-On (SSO) authentication errors and SCIM user provisioning sync issues.

🔑 Single Sign-On (SSO) Troubles

Issue 1: Single Sign-On (SSO) login fails with a claim or attribute error

• Symptom: Employees attempting to sign in via corporate SSO receive an attribute error during redirection.
• Cause: Your identity provider's SAML claim names do not match the expected email claim schema configured in Algus.
• Solution:
  1. An administrator opens Settings → SSO Integration → SAML Setup.
  2. Verify the Email Attribute Mapping string matches the exact claim key sent by your identity provider (e.g., http://schemas.xmlsoap.org/ws/2005/05/identity/claims/emailaddress or email).
  3. Alternatively, click Fetch Metadata to auto-sync SAML claim definitions.

Issue 2: SCIM user provisioning fails to create new users automatically

• Symptom: New employees added to your corporate identity provider (Microsoft Entra or Okta) are not being automatically created in Algus.
• Cause: The SCIM secret bearer token has expired or was entered incorrectly in your identity provider portal.
• Solution:
  1. An administrator opens Settings → SSO Integration → SCIM Provisioning tab.
  2. Click Generate Token to create a fresh secret bearer token.
  3. Copy the token immediately and update the SCIM authentication token field in your corporate identity provider portal.
  4. Test provisioning from your identity provider dashboard to confirm connectivity.