Skip to content

feat: add disable_jit to enterprise + saml connection update params and responses - #566

Draft
NicolasLopes7 wants to merge 1 commit into
v3from
nicolas/disable-jit-self-serve
Draft

feat: add disable_jit to enterprise + saml connection update params and responses#566
NicolasLopes7 wants to merge 1 commit into
v3from
nicolas/disable-jit-self-serve

Conversation

@NicolasLopes7

@NicolasLopes7 NicolasLopes7 commented Jun 9, 2026

Copy link
Copy Markdown
Contributor

What

Adds disable_jit support to the Enterprise Connections and (legacy) SAML Connections Backend API bindings.

When disable_jit is set on an enterprise connection, JIT (Just-In-Time) provisioning is disabled for SAML sign-in: users without an existing account receive ExternalAccountNotFound instead of being auto-provisioned. It is a self-serve, per-connection setting managed via the BAPI update endpoints.

Changes

  • EnterpriseConnection.DisableJIT and SAMLConnection.DisableJIT (bool) — read field on the response structs.
  • enterpriseconnection.UpdateParams.DisableJIT and samlconnection.UpdateParams.DisableJIT (*bool, json disable_jit,omitempty) — top-level update param on both packages.
  • Round-trip tests for both Update methods (request body contains "disable_jit":true; response deserializes into DisableJIT == true).

Notes

  • Targets v3.
  • Not added to CreateParams — the BAPI only accepts disable_jit on update.

Backend

Backend counterpart (column + BAPI + serializer): clerk/clerk_go#19496

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant