vibecodng.com

Free MCP betaIndex and tools live

Measured entry

hextaui-settings-sso

formminimal-flat

A client-side SSO settings card for listing providers, enabling SSO, testing connections, copying metadata, and creating or deleting providers through callback props. It ships as a HextaUI shadcn registry block and depends on React, Lucide icons, the cn utility, and a broad set of shadcn primitives backed by Radix.

Specimen
Harness screenshot of hextaui-settings-sso at 375 pixels wide
Harness screenshot at 375 pixels wide. No horizontal overflow recorded.
Harness screenshot of hextaui-settings-sso at 768 pixels wide
Harness screenshot at 768 pixels wide. No horizontal overflow recorded.
Harness screenshot of hextaui-settings-sso at 1440 pixels wide
Harness screenshot at 1440 pixels wide. No horizontal overflow recorded.

Measured

Every value below was written by the harness on the run that produced the frames above. None of it is derived from the prose.

Harness measurements recorded for hextaui-settings-sso
BuildOK
MountOK
Console errors0
Uncaught page errors0
Horizontal overflowclean at 375, 768, 1440
Axe critical0
Axe serious0
Axe moderate0
Axe minor0
Gzip marginal73.4 KB (138.8 KB build, 65.4 KB baseline)
Bare modeFAIL
Provider requiredNO
Demo usedwritten from the component source API

What the harness recorded

BARE BUILD

✗ Build failed in 1m 18s
error during build:
[vite:load-fallback] Could not load <sandbox>/src/lib/utils (imported by src/cut/blocks/settings/settings-sso.tsx): ENOENT: no such file or directory, open '<sandbox>/src/lib/utils'

Verdict

A credible admin UI starting point with clean responsive behavior and no detected accessibility issues, but it is not drop-in infrastructure. It needs a shadcn-style setup to mount, and teams must wire every operation plus expand the non-SAML flows before treating it as production SSO management.

Use it if

  • You need an organization settings surface for SAML providers with empty, active, pending, and error states.
  • Your app already uses shadcn conventions and can connect the supplied create, update, delete, test, and toggle callbacks to real APIs.
  • You want responsive provider controls with confirmation before deletion and accessible dialog primitives.

Skip it if

  • Your project does not use shadcn aliases, theme tokens, and shared UI primitives, and you do not want to recreate that foundation.
  • You need complete OAuth or OpenID Connect configuration fields because the creation dialog only exposes detailed settings for SAML.
  • You want a self-contained SSO implementation because this block supplies presentation and callback hooks, not authentication or persistence.
  • You need a lean form with few dependencies because this block pulls in many shared controls and dialog primitives.

Install

Installation record for hextaui-settings-sso
Declared dependencies@radix-ui/react-alert-dialog, @radix-ui/react-slot, @radix-ui/react-dialog, @radix-ui/react-label, @radix-ui/react-separator, @radix-ui/react-select, @radix-ui/react-switch
Missing on installnone
Bare installfails once the shadcn-style helpers are removed, so it needs that setup
Providerno provider required in the harness

In a non-shadcn project, add React and Lucide, install or recreate the alert dialog, badge, button, card, dialog, field, input group, select, switch, and textarea components, provide the cn class helper and matching import aliases, and supply the Tailwind utilities and theme tokens those components expect. Then connect all callback props to your backend.

Source and credit

This page is a review, not a copy. The component source lives with its author and this site does not republish it. Read the license before you use anything.

Author repository

github.com/preetsuthar17/HextaUI
License
MIT
Record published
2026-08-14

Alternatives

Other published entries for the form pattern, ordered by what they measured: mounts first, then clean axe scans, then bare-mode passes, then the smaller bundle.