Home Troubleshooting Troubleshooting SAML/OIDC Integration Issues in Schedly

Troubleshooting SAML/OIDC Integration Issues in Schedly

Last updated on Jul 07, 2026

Overview

Integrating SAML/OIDC for Single Sign-On (SSO) in Schedly facilitates secure and seamless user authentication, leveraging your organization's existing identity provider protocols. Common challenges during integration include authentication errors and SSO connectivity issues, which can affect user access to the Schedly platform. This article provides a systematic approach to diagnosing and resolving these issues.

Prerequisites

  • Ensure your organization supports SAML/OIDC protocols.
  • Have administrative rights to manage SSO settings within your identity provider.
  • Access to Schedly's API & Developer Tools from the overview section.

Step-by-Step Instructions

Identifying the Issue

  1. Log in to Schedly using one of the secure methods provided.
  2. Navigate to the API & Developer Tools section.
  3. Access Single Sign-On Settings and review the configurations.

Troubleshooting Checklist

  1. Verify Identity Provider Settings:
    • Confirm that all necessary fields in your identity provider's settings match the configurations in Schedly, such as metadata URLs, entity IDs, and certificates.
  2. Check SAML/OIDC Credentials:
    • Ensure the client ID, client secret, or SAML certificates are correctly entered.
  3. Synchronize System Clocks:
    • Make sure the server clocks of both Schedly and the identity provider are perfectly synchronized to prevent token expiration issues.

Resolving Authentication Errors

  1. Reconfigure SAML/OIDC Details:
    • Click Settings > Single Sign-On.
    • Double-check and update all fields including the SSO URL and Binding Type.
  2. Testing Authentication Pathways:
    • Go to the Schedly login page, select Sign in with SAML/OIDC and attempt to log in.

Debugging SSO Connectivity

  1. Access Audit Logs:
    • From the API & Developer Tools, locate the Audit Logs section to review detailed logs of authentication attempts and errors.
    • Look for common error codes like 401 (Unauthorized) or 403 (Forbidden).
  2. Review Network Connectivity:
    • Ensure there are no firewall rules or network policies blocking requests between Schedly and your identity provider.

Accessing Integration Logs

  1. Visit the API & Developer Tools section in Schedly.
  2. Click on Integration Logs for an in-depth view of any issues related to SAML/OIDC execution.

Key Details & Limits

  • Maximum authentication token expiry is 24 hours.
  • SAML/OIDC is supported on all Schedly plans.
  • Log access requires administrator permissions in Schedly.

Frequently Asked Questions

  1. What if the "Sign in with SAML/OIDC" button isn't working?
    • Verify the button setup in Schedly matches your identity provider configurations.
  2. Can I change the identity provider without resetting configurations?
    • No, changing providers involves updating all related credentials and URLs.
  3. Why am I receiving a "403 Forbidden" error?
    • Check your identity provider permissions to ensure Schedly is whitelisted.
  4. How can I test SAML/OIDC integration before rolling it out?
    • Use a test account to verify all login flows work correctly before full deployment.
  5. What happens if my SAML certificate expires?
    • Renew the certificate with your identity provider and update it in Schedly immediately.

Troubleshooting

  • SSO Login Fails Despite Correct Credentials:
    • Revisit the identity provider setup and ensure all IDs and secrets are set correctly.
  • Unable to Access Integration Logs:
    • Confirm you have the necessary admin rights in Schedly to view these logs.

Related Topics

  • How to Configure SAML/OIDC in Schedly: Step-by-step setup guide.
  • Using API & Developer Tools in Schedly: Overview and capabilities.
  • Understanding Schedly's Security Features: Key security aspects to consider.
  • Managing User Permissions in Schedly: Assigning and managing user access.