Skip to content

feat(ui,localizations,shared): add the organization Security page SSO overview#8813

Draft
iagodahlem wants to merge 5 commits into
iago/orgs-1603-configure-sso-data-ownershipfrom
iago/orgs-1603-security-page-ui
Draft

feat(ui,localizations,shared): add the organization Security page SSO overview#8813
iagodahlem wants to merge 5 commits into
iago/orgs-1603-configure-sso-data-ownershipfrom
iago/orgs-1603-security-page-ui

Conversation

@iagodahlem

Copy link
Copy Markdown
Member

The Security page in <OrganizationProfile /> now renders an SSO overview instead of dropping straight into the configuration wizard:

  • Connection state at a glance — a status badge (Unconfigured / In Progress / Active / Inactive) driven by the connection entity's status, with per-state copy and actions (Start configuration / Continue configuration)
  • Enable SSO toggle — optimistic, gated on a successful test run
  • Inline configuration details — Provider (icon + name), Domain chips (multi-domain wraps), Sign on URL, Issuer, and Certificate, truncating with ellipsis + full-value tooltips for long SAML values
  • ⋯ menu — Edit (re-enters the wizard) and Delete (type-to-confirm using the organization name; lands back on the overview without a remount)

Start / Continue / Edit switch the page into the existing wizard via local view state — the temporary navigation until the wizard gets its back-to-Security header in the integration follow-up.

Under the hood: the page reads only the umbrella enterprise-connection hook and passes data down as props (the wizard's provider stays internal to the wizard), and ResetConnectionDialog is now context-free (hosts pass the delete action and portal root), so the page reuses it outside the wizard. Wizard behavior is unchanged.

States verified against design in light and dark. Known gaps deferred to the wizard-integration follow-up: Edit currently lands on the guard-derived step (the confirmation step for an active connection) rather than forcing step 1, and there's no in-wizard way back to the overview yet.

ORGS-1603. Stacked on #8799.

@vercel

vercel Bot commented Jun 10, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
clerk-js-sandbox Ready Ready Preview, Comment Jun 10, 2026 8:15pm

Request Review

@changeset-bot

changeset-bot Bot commented Jun 10, 2026

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: 8ab736d

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 20 packages
Name Type
@clerk/localizations Patch
@clerk/shared Patch
@clerk/ui Patch
@clerk/react Patch
@clerk/astro Patch
@clerk/backend Patch
@clerk/chrome-extension Patch
@clerk/clerk-js Patch
@clerk/expo-passkeys Patch
@clerk/expo Patch
@clerk/express Patch
@clerk/fastify Patch
@clerk/hono Patch
@clerk/msw Patch
@clerk/nextjs Patch
@clerk/nuxt Patch
@clerk/react-router Patch
@clerk/tanstack-react-start Patch
@clerk/testing Patch
@clerk/vue Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@coderabbitai

coderabbitai Bot commented Jun 10, 2026

Copy link
Copy Markdown
Contributor

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository YAML (base), Repository UI (inherited)

Review profile: CHILL

Plan: Pro

Run ID: 19681aec-5a4d-4356-9aea-9d37637c83c1

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review

Comment @coderabbitai help to get the list of available commands and usage tips.

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant