Skip to main content

Troubleshoot: Glean and Ironclad Connector

The Glean–Ironclad connector lets Glean index your Ironclad workflows, repository records, and contract documents through a secure, OAuth-based API integration, while continuing to enforce the same SSO, SAML, and record-level permissions your users already have in Ironclad.

There is no “out-of-the-box integration” built by Ironclad itself, but many customers run Glean successfully in production. Ironclad supports it via our public API and OAuth framework and requires that API access is enabled.

To learn more about the connector, refer to Glean and Ironclad Connector.

Permissions

Features

API, Glean

Permissions

You must be an Ironclad Admin and a Glean admin to connect Glean with Ironclad.
You must have API access to create the OAuth app and let Glean call Ironclad’s APIs.

Before You Begin

Before debugging specific errors, confirm these basics:

  • API access is enabled in Ironclad

    • The Glean connector uses Ironclad’s public API. API access must be enabled in your Ironclad environment.

  • You have the right admin permissions

    • In Ironclad: You can access Company Settings → API → Apps and create/manage OAuth apps.

    • In Glean: You’re a Glean admin / data source admin with rights to configure the Ironclad connector.

  • User identity matches across tools

    • The email used to sign into Glean matches the user’s email in Ironclad. Ironclad enforces permissions based on that identity; mismatches can cause missing data or 403s even when the connector is “on.”


Common Connector Problems

This table summarizes the most common Glean–Ironclad connector issues, their likely causes, and the fastest checks to run first. Refer to it as a quick triage tool before you dive into deeper troubleshooting or open a support ticket:

Problem

Likely cause

Solution

“Login loop” / cannot complete authorization

Domain or SSO (SAML) mismatch between Ironclad, Glean, and your IdP

  1. Confirm your Ironclad URL (e.g., https://na1.ironcladapp.com)

  2. In Okta/Entra, set Entity ID / Audience and Reply URLs/ACS to that host.

  3. In Glean, set Server domain accordingly (e.g., na1). Verify that it matches your SSO/SCIM domain.

  4. Retry in a private/incognito window.

Bad URL or 500 “Internal Server Error” on authorize

Incorrect Server domain in Glean or redirect URI mismatch

  1. In Ironclad’s OAuth app, ensure the Redirect URI exactly matches Glean’s value.

  2. In Glean, correct Server domain (e.g., na1 for https://na1.ironcladapp.com).

  3. If a 500 persists, capture a HAR and contact Glean Support.

Admin can connect, others can’t keep the toggle on

Same domain/SSO issues for some users, or Glean not persisting state

  1. Confirm all users go through the same Ironclad URL and SAML app (no manual URL edits).

  2. Capture HARs for a working admin and a failing user.

  3. Share with Ironclad Support to confirm OAuth success, then with Glean Support to review connector state.

Errors in Ironclad Sandbox / Open Sandbox

Glean connector is not supported in Sandbox/Open Sandbox

  1. Check which Ironclad environment you’re targeting.

  2. Re‑point the connector to a supported tenant (production or a non‑sandbox demo/stage).

Users connect but see missing data or 403s

Email/identity mismatch or insufficient Ironclad permissions

  1. Verify Glean and Ironclad use the same email for the user.

  2. Confirm the user can see the same records directly in Ironclad.

  3. If not, adjust Ironclad roles/groups/record access and re‑test.


Ownership and Support Boundaries

Ironclad Responsibilities

Ironclad provides the API, OAuth framework, and configuration guidance needed for a secure connection (for example, helping validate OAuth app scopes, redirect URIs, and SAML domain alignment).

Glean Responsibilities

The connector is built, shipped, and owned by Glean. Glean owns the connector’s internal behavior (for example, how callbacks are handled, how tokens are persisted, and how the Ironclad data source toggle is managed). When Ironclad confirms that OAuth and SSO are working correctly but the Glean data source toggle does not stay on, you should continue troubleshooting with Glean Support.

Resources

Explore articles, courses, and support options to get the most out of Ironclad.

Help Center

Academy

  • No relevant content at this time.

Support

Did this answer your question?