chore(ui): Add wizard steps to `<ConfigureSSO />` by LauraBeatris · Pull Request #8468 · clerk/javascript

LauraBeatris · 2026-05-04T18:34:03Z

Description

Introduces Wizard component with support for root and inner steps
Introduce basic boilerplate of modules per step
Add different Flow.Part per step type
Handles initial loading UI state when querying enterprise connections

To be handled in next PRs:

Whether a step is considered "complete" (green mark)

CleanShot.2026-05-05.at.00.18.48.mp4

Checklist

pnpm test runs as expected.
pnpm build runs as expected.
(If applicable) JSDoc comments have been added or updated for any package exports
(If applicable) Documentation has been updated

Type of change

changeset-bot · 2026-05-04T18:34:07Z

🦋 Changeset detected

Latest commit: a7f1340

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

This PR includes changesets to release 2 packages

Name	Type
@clerk/ui	Patch
@clerk/chrome-extension	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

vercel · 2026-05-04T18:34:08Z

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

Project	Deployment	Actions	Updated (UTC)
clerk-js-sandbox	Ready	Preview, Comment	May 5, 2026 11:11pm

LauraBeatris · 2026-05-05T21:47:22Z

 return;
 }

+ if (noUserExists(this)) {


Added this one that got missed on the first PR

iagodahlem

The declarative shape is great 👏 — I think we still need some improvements to better structure it and separate the wizard responsibilities into more layers, so we can easily extract those components for reuse later, but I think it's good enough as it is for now and we can follow up. Just two small alignment items I'd flag for this PR before the bigger refactor lands as a follow-up:

Flow.Part part= naming convention.
isLoading flowing through ConfigureSSOFlowContext.

iagodahlem · 2026-05-06T10:50:30Z

+ label='Configure'
+ >
+ <ConfigureSSOWizard>
+ {/* TODO: Implement configure steps */}


Suggested change
{/* TODO: Implement configure steps */}

iagodahlem · 2026-05-06T13:10:19Z

+ >
+ <ConfigureSSOFlowProvider
+ enterpriseConnection={enterpriseConnection}
+ isLoading={isLoadingEnterpriseConnections}


I think passing the initial isLoading down to the context and rendering it on the wizard might lead us to issues when invalidating the query, and also for instance, when we start determining the current step after a refresh I think it would be good to have the loading before the wizard even renders, so what do you think of lifting the initial loading state here to ConfigureSSO root? Something like:
constAuthenticatedContent=withCoreUserGuard(()=>{const{ data, isLoading }=__internal_useUserEnterpriseConnections({enabled: true});if(isLoading&&!data){return<FullSpinner/>;}return(// …existing layout…<ConfigureSSOFlowProviderenterpriseConnection={data?.[0]}><ConfigureSSOSteps/></ConfigureSSOFlowProvider>);});
Happy to take this as a separate PR if you'd rather keep this one tight.

iagodahlem · 2026-05-06T13:13:15Z

+
+export const TestConfigurationStep = (): JSX.Element => {
+ return (
+ <Flow.Part part='test-sso'>


I think the convention for Flow.Part part= is camelCase across Sign-In / Sign-Up / SessionTasks / UserVerification (phoneCode2Fa, alternativeMethods, enterpriseConnections, chooseOrganization, etc.). The four other ConfigureSSO steps already follow that — only test-sso here and sso-confirmation in ConfirmationStep are kebab-case.

LauraBeatris · 2026-05-04T18:34:03Z

Description

Introduces Wizard component with support for root and inner steps
Introduce basic boilerplate of modules per step
Add different Flow.Part per step type
Handles initial loading UI state when querying enterprise connections

To be handled in next PRs:

Whether a step is considered "complete" (green mark)

CleanShot.2026-05-05.at.00.18.48.mp4

Checklist

pnpm test runs as expected.
pnpm build runs as expected.
(If applicable) JSDoc comments have been added or updated for any package exports
(If applicable) Documentation has been updated

Type of change

changeset-bot · 2026-05-04T18:34:07Z

🦋 Changeset detected

Latest commit: a7f1340

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

This PR includes changesets to release 2 packages

Name	Type
@clerk/ui	Patch
@clerk/chrome-extension	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

vercel · 2026-05-04T18:34:08Z

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

Project	Deployment	Actions	Updated (UTC)
clerk-js-sandbox	Ready	Preview, Comment	May 5, 2026 11:11pm

LauraBeatris · 2026-05-05T21:47:22Z

 return;
 }

+ if (noUserExists(this)) {


Added this one that got missed on the first PR

iagodahlem

The declarative shape is great 👏 — I think we still need some improvements to better structure it and separate the wizard responsibilities into more layers, so we can easily extract those components for reuse later, but I think it's good enough as it is for now and we can follow up. Just two small alignment items I'd flag for this PR before the bigger refactor lands as a follow-up:

Flow.Part part= naming convention.
isLoading flowing through ConfigureSSOFlowContext.

iagodahlem · 2026-05-06T10:50:30Z

+ label='Configure'
+ >
+ <ConfigureSSOWizard>
+ {/* TODO: Implement configure steps */}


Suggested change
{/* TODO: Implement configure steps */}

iagodahlem · 2026-05-06T13:10:19Z

+ >
+ <ConfigureSSOFlowProvider
+ enterpriseConnection={enterpriseConnection}
+ isLoading={isLoadingEnterpriseConnections}


I think passing the initial isLoading down to the context and rendering it on the wizard might lead us to issues when invalidating the query, and also for instance, when we start determining the current step after a refresh I think it would be good to have the loading before the wizard even renders, so what do you think of lifting the initial loading state here to ConfigureSSO root? Something like:
constAuthenticatedContent=withCoreUserGuard(()=>{const{ data, isLoading }=__internal_useUserEnterpriseConnections({enabled: true});if(isLoading&&!data){return<FullSpinner/>;}return(// …existing layout…<ConfigureSSOFlowProviderenterpriseConnection={data?.[0]}><ConfigureSSOSteps/></ConfigureSSOFlowProvider>);});
Happy to take this as a separate PR if you'd rather keep this one tight.

iagodahlem · 2026-05-06T13:13:15Z

+
+export const TestConfigurationStep = (): JSX.Element => {
+ return (
+ <Flow.Part part='test-sso'>


I think the convention for Flow.Part part= is camelCase across Sign-In / Sign-Up / SessionTasks / UserVerification (phoneCode2Fa, alternativeMethods, enterpriseConnections, chooseOrganization, etc.). The four other ConfigureSSO steps already follow that — only test-sso here and sso-confirmation in ConfirmationStep are kebab-case.

LauraBeatris · 2026-05-04T18:34:03Z

Description

Introduces Wizard component with support for root and inner steps
Introduce basic boilerplate of modules per step
Add different Flow.Part per step type
Handles initial loading UI state when querying enterprise connections

To be handled in next PRs:

Whether a step is considered "complete" (green mark)

CleanShot.2026-05-05.at.00.18.48.mp4

Checklist

pnpm test runs as expected.
pnpm build runs as expected.
(If applicable) JSDoc comments have been added or updated for any package exports
(If applicable) Documentation has been updated

Type of change

changeset-bot · 2026-05-04T18:34:07Z

🦋 Changeset detected

Latest commit: a7f1340

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

This PR includes changesets to release 2 packages

Name	Type
@clerk/ui	Patch
@clerk/chrome-extension	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

vercel · 2026-05-04T18:34:08Z

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

Project	Deployment	Actions	Updated (UTC)
clerk-js-sandbox	Ready	Preview, Comment	May 5, 2026 11:11pm

LauraBeatris · 2026-05-05T21:47:22Z

 return;
 }

+ if (noUserExists(this)) {


Added this one that got missed on the first PR

iagodahlem

The declarative shape is great 👏 — I think we still need some improvements to better structure it and separate the wizard responsibilities into more layers, so we can easily extract those components for reuse later, but I think it's good enough as it is for now and we can follow up. Just two small alignment items I'd flag for this PR before the bigger refactor lands as a follow-up:

Flow.Part part= naming convention.
isLoading flowing through ConfigureSSOFlowContext.

iagodahlem · 2026-05-06T10:50:30Z

+ label='Configure'
+ >
+ <ConfigureSSOWizard>
+ {/* TODO: Implement configure steps */}


Suggested change
{/* TODO: Implement configure steps */}

iagodahlem · 2026-05-06T13:10:19Z

+ >
+ <ConfigureSSOFlowProvider
+ enterpriseConnection={enterpriseConnection}
+ isLoading={isLoadingEnterpriseConnections}


I think passing the initial isLoading down to the context and rendering it on the wizard might lead us to issues when invalidating the query, and also for instance, when we start determining the current step after a refresh I think it would be good to have the loading before the wizard even renders, so what do you think of lifting the initial loading state here to ConfigureSSO root? Something like:
constAuthenticatedContent=withCoreUserGuard(()=>{const{ data, isLoading }=__internal_useUserEnterpriseConnections({enabled: true});if(isLoading&&!data){return<FullSpinner/>;}return(// …existing layout…<ConfigureSSOFlowProviderenterpriseConnection={data?.[0]}><ConfigureSSOSteps/></ConfigureSSOFlowProvider>);});
Happy to take this as a separate PR if you'd rather keep this one tight.

iagodahlem · 2026-05-06T13:13:15Z

+
+export const TestConfigurationStep = (): JSX.Element => {
+ return (
+ <Flow.Part part='test-sso'>


I think the convention for Flow.Part part= is camelCase across Sign-In / Sign-Up / SessionTasks / UserVerification (phoneCode2Fa, alternativeMethods, enterpriseConnections, chooseOrganization, etc.). The four other ConfigureSSO steps already follow that — only test-sso here and sso-confirmation in ConfirmationStep are kebab-case.

LauraBeatris · 2026-05-04T18:34:03Z

Description

Introduces Wizard component with support for root and inner steps
Introduce basic boilerplate of modules per step
Add different Flow.Part per step type
Handles initial loading UI state when querying enterprise connections

To be handled in next PRs:

Whether a step is considered "complete" (green mark)

CleanShot.2026-05-05.at.00.18.48.mp4

Checklist

pnpm test runs as expected.
pnpm build runs as expected.
(If applicable) JSDoc comments have been added or updated for any package exports
(If applicable) Documentation has been updated

Type of change

changeset-bot · 2026-05-04T18:34:07Z

🦋 Changeset detected

Latest commit: a7f1340

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

This PR includes changesets to release 2 packages

Name	Type
@clerk/ui	Patch
@clerk/chrome-extension	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

vercel · 2026-05-04T18:34:08Z

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

Project	Deployment	Actions	Updated (UTC)
clerk-js-sandbox	Ready	Preview, Comment	May 5, 2026 11:11pm

LauraBeatris · 2026-05-05T21:47:22Z

 return;
 }

+ if (noUserExists(this)) {


Added this one that got missed on the first PR

iagodahlem

The declarative shape is great 👏 — I think we still need some improvements to better structure it and separate the wizard responsibilities into more layers, so we can easily extract those components for reuse later, but I think it's good enough as it is for now and we can follow up. Just two small alignment items I'd flag for this PR before the bigger refactor lands as a follow-up:

Flow.Part part= naming convention.
isLoading flowing through ConfigureSSOFlowContext.

iagodahlem · 2026-05-06T10:50:30Z

+ label='Configure'
+ >
+ <ConfigureSSOWizard>
+ {/* TODO: Implement configure steps */}


Suggested change
{/* TODO: Implement configure steps */}

iagodahlem · 2026-05-06T13:10:19Z

+ >
+ <ConfigureSSOFlowProvider
+ enterpriseConnection={enterpriseConnection}
+ isLoading={isLoadingEnterpriseConnections}


I think passing the initial isLoading down to the context and rendering it on the wizard might lead us to issues when invalidating the query, and also for instance, when we start determining the current step after a refresh I think it would be good to have the loading before the wizard even renders, so what do you think of lifting the initial loading state here to ConfigureSSO root? Something like:
constAuthenticatedContent=withCoreUserGuard(()=>{const{ data, isLoading }=__internal_useUserEnterpriseConnections({enabled: true});if(isLoading&&!data){return<FullSpinner/>;}return(// …existing layout…<ConfigureSSOFlowProviderenterpriseConnection={data?.[0]}><ConfigureSSOSteps/></ConfigureSSOFlowProvider>);});
Happy to take this as a separate PR if you'd rather keep this one tight.

iagodahlem · 2026-05-06T13:13:15Z

+
+export const TestConfigurationStep = (): JSX.Element => {
+ return (
+ <Flow.Part part='test-sso'>


I think the convention for Flow.Part part= is camelCase across Sign-In / Sign-Up / SessionTasks / UserVerification (phoneCode2Fa, alternativeMethods, enterpriseConnections, chooseOrganization, etc.). The four other ConfigureSSO steps already follow that — only test-sso here and sso-confirmation in ConfirmationStep are kebab-case.

LauraBeatris · 2026-05-04T18:34:03Z

Description

Introduces Wizard component with support for root and inner steps
Introduce basic boilerplate of modules per step
Add different Flow.Part per step type
Handles initial loading UI state when querying enterprise connections

To be handled in next PRs:

Whether a step is considered "complete" (green mark)

CleanShot.2026-05-05.at.00.18.48.mp4

Checklist

pnpm test runs as expected.
pnpm build runs as expected.
(If applicable) JSDoc comments have been added or updated for any package exports
(If applicable) Documentation has been updated

Type of change

changeset-bot · 2026-05-04T18:34:07Z

🦋 Changeset detected

Latest commit: a7f1340

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

This PR includes changesets to release 2 packages

Name	Type
@clerk/ui	Patch
@clerk/chrome-extension	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

vercel · 2026-05-04T18:34:08Z

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

Project	Deployment	Actions	Updated (UTC)
clerk-js-sandbox	Ready	Preview, Comment	May 5, 2026 11:11pm

LauraBeatris · 2026-05-05T21:47:22Z

 return;
 }

+ if (noUserExists(this)) {


Added this one that got missed on the first PR

iagodahlem

The declarative shape is great 👏 — I think we still need some improvements to better structure it and separate the wizard responsibilities into more layers, so we can easily extract those components for reuse later, but I think it's good enough as it is for now and we can follow up. Just two small alignment items I'd flag for this PR before the bigger refactor lands as a follow-up:

Flow.Part part= naming convention.
isLoading flowing through ConfigureSSOFlowContext.

iagodahlem · 2026-05-06T10:50:30Z

+ label='Configure'
+ >
+ <ConfigureSSOWizard>
+ {/* TODO: Implement configure steps */}


Suggested change
{/* TODO: Implement configure steps */}

iagodahlem · 2026-05-06T13:10:19Z

+ >
+ <ConfigureSSOFlowProvider
+ enterpriseConnection={enterpriseConnection}
+ isLoading={isLoadingEnterpriseConnections}


I think passing the initial isLoading down to the context and rendering it on the wizard might lead us to issues when invalidating the query, and also for instance, when we start determining the current step after a refresh I think it would be good to have the loading before the wizard even renders, so what do you think of lifting the initial loading state here to ConfigureSSO root? Something like:
constAuthenticatedContent=withCoreUserGuard(()=>{const{ data, isLoading }=__internal_useUserEnterpriseConnections({enabled: true});if(isLoading&&!data){return<FullSpinner/>;}return(// …existing layout…<ConfigureSSOFlowProviderenterpriseConnection={data?.[0]}><ConfigureSSOSteps/></ConfigureSSOFlowProvider>);});
Happy to take this as a separate PR if you'd rather keep this one tight.

iagodahlem · 2026-05-06T13:13:15Z

+
+export const TestConfigurationStep = (): JSX.Element => {
+ return (
+ <Flow.Part part='test-sso'>


I think the convention for Flow.Part part= is camelCase across Sign-In / Sign-Up / SessionTasks / UserVerification (phoneCode2Fa, alternativeMethods, enterpriseConnections, chooseOrganization, etc.). The four other ConfigureSSO steps already follow that — only test-sso here and sso-confirmation in ConfirmationStep are kebab-case.

LauraBeatris · 2026-05-04T18:34:03Z

Description

Introduces Wizard component with support for root and inner steps
Introduce basic boilerplate of modules per step
Add different Flow.Part per step type
Handles initial loading UI state when querying enterprise connections

To be handled in next PRs:

Whether a step is considered "complete" (green mark)

CleanShot.2026-05-05.at.00.18.48.mp4

Checklist

pnpm test runs as expected.
pnpm build runs as expected.
(If applicable) JSDoc comments have been added or updated for any package exports
(If applicable) Documentation has been updated

Type of change

changeset-bot · 2026-05-04T18:34:07Z

🦋 Changeset detected

Latest commit: a7f1340

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

This PR includes changesets to release 2 packages

Name	Type
@clerk/ui	Patch
@clerk/chrome-extension	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

vercel · 2026-05-04T18:34:08Z

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

Project	Deployment	Actions	Updated (UTC)
clerk-js-sandbox	Ready	Preview, Comment	May 5, 2026 11:11pm

LauraBeatris · 2026-05-05T21:47:22Z

 return;
 }

+ if (noUserExists(this)) {


Added this one that got missed on the first PR

iagodahlem

The declarative shape is great 👏 — I think we still need some improvements to better structure it and separate the wizard responsibilities into more layers, so we can easily extract those components for reuse later, but I think it's good enough as it is for now and we can follow up. Just two small alignment items I'd flag for this PR before the bigger refactor lands as a follow-up:

Flow.Part part= naming convention.
isLoading flowing through ConfigureSSOFlowContext.

iagodahlem · 2026-05-06T10:50:30Z

+ label='Configure'
+ >
+ <ConfigureSSOWizard>
+ {/* TODO: Implement configure steps */}


Suggested change
{/* TODO: Implement configure steps */}

iagodahlem · 2026-05-06T13:10:19Z

+ >
+ <ConfigureSSOFlowProvider
+ enterpriseConnection={enterpriseConnection}
+ isLoading={isLoadingEnterpriseConnections}


I think passing the initial isLoading down to the context and rendering it on the wizard might lead us to issues when invalidating the query, and also for instance, when we start determining the current step after a refresh I think it would be good to have the loading before the wizard even renders, so what do you think of lifting the initial loading state here to ConfigureSSO root? Something like:
constAuthenticatedContent=withCoreUserGuard(()=>{const{ data, isLoading }=__internal_useUserEnterpriseConnections({enabled: true});if(isLoading&&!data){return<FullSpinner/>;}return(// …existing layout…<ConfigureSSOFlowProviderenterpriseConnection={data?.[0]}><ConfigureSSOSteps/></ConfigureSSOFlowProvider>);});
Happy to take this as a separate PR if you'd rather keep this one tight.

iagodahlem · 2026-05-06T13:13:15Z

+
+export const TestConfigurationStep = (): JSX.Element => {
+ return (
+ <Flow.Part part='test-sso'>


I think the convention for Flow.Part part= is camelCase across Sign-In / Sign-Up / SessionTasks / UserVerification (phoneCode2Fa, alternativeMethods, enterpriseConnections, chooseOrganization, etc.). The four other ConfigureSSO steps already follow that — only test-sso here and sso-confirmation in ConfirmationStep are kebab-case.

LauraBeatris · 2026-05-04T18:34:03Z

Description

Introduces Wizard component with support for root and inner steps
Introduce basic boilerplate of modules per step
Add different Flow.Part per step type
Handles initial loading UI state when querying enterprise connections

To be handled in next PRs:

Whether a step is considered "complete" (green mark)

CleanShot.2026-05-05.at.00.18.48.mp4

Checklist

pnpm test runs as expected.
pnpm build runs as expected.
(If applicable) JSDoc comments have been added or updated for any package exports
(If applicable) Documentation has been updated

Type of change

changeset-bot · 2026-05-04T18:34:07Z

🦋 Changeset detected

Latest commit: a7f1340

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

This PR includes changesets to release 2 packages

Name	Type
@clerk/ui	Patch
@clerk/chrome-extension	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

vercel · 2026-05-04T18:34:08Z

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

Project	Deployment	Actions	Updated (UTC)
clerk-js-sandbox	Ready	Preview, Comment	May 5, 2026 11:11pm

LauraBeatris · 2026-05-05T21:47:22Z

 return;
 }

+ if (noUserExists(this)) {


Added this one that got missed on the first PR

iagodahlem

The declarative shape is great 👏 — I think we still need some improvements to better structure it and separate the wizard responsibilities into more layers, so we can easily extract those components for reuse later, but I think it's good enough as it is for now and we can follow up. Just two small alignment items I'd flag for this PR before the bigger refactor lands as a follow-up:

Flow.Part part= naming convention.
isLoading flowing through ConfigureSSOFlowContext.

iagodahlem · 2026-05-06T10:50:30Z

+ label='Configure'
+ >
+ <ConfigureSSOWizard>
+ {/* TODO: Implement configure steps */}


Suggested change
{/* TODO: Implement configure steps */}

iagodahlem · 2026-05-06T13:10:19Z

+ >
+ <ConfigureSSOFlowProvider
+ enterpriseConnection={enterpriseConnection}
+ isLoading={isLoadingEnterpriseConnections}


I think passing the initial isLoading down to the context and rendering it on the wizard might lead us to issues when invalidating the query, and also for instance, when we start determining the current step after a refresh I think it would be good to have the loading before the wizard even renders, so what do you think of lifting the initial loading state here to ConfigureSSO root? Something like:
constAuthenticatedContent=withCoreUserGuard(()=>{const{ data, isLoading }=__internal_useUserEnterpriseConnections({enabled: true});if(isLoading&&!data){return<FullSpinner/>;}return(// …existing layout…<ConfigureSSOFlowProviderenterpriseConnection={data?.[0]}><ConfigureSSOSteps/></ConfigureSSOFlowProvider>);});
Happy to take this as a separate PR if you'd rather keep this one tight.

iagodahlem · 2026-05-06T13:13:15Z

+
+export const TestConfigurationStep = (): JSX.Element => {
+ return (
+ <Flow.Part part='test-sso'>


I think the convention for Flow.Part part= is camelCase across Sign-In / Sign-Up / SessionTasks / UserVerification (phoneCode2Fa, alternativeMethods, enterpriseConnections, chooseOrganization, etc.). The four other ConfigureSSO steps already follow that — only test-sso here and sso-confirmation in ConfirmationStep are kebab-case.

LauraBeatris · 2026-05-04T18:34:03Z

Description

Introduces Wizard component with support for root and inner steps
Introduce basic boilerplate of modules per step
Add different Flow.Part per step type
Handles initial loading UI state when querying enterprise connections

To be handled in next PRs:

Whether a step is considered "complete" (green mark)

CleanShot.2026-05-05.at.00.18.48.mp4

Checklist

pnpm test runs as expected.
pnpm build runs as expected.
(If applicable) JSDoc comments have been added or updated for any package exports
(If applicable) Documentation has been updated

Type of change

changeset-bot · 2026-05-04T18:34:07Z

🦋 Changeset detected

Latest commit: a7f1340

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

This PR includes changesets to release 2 packages

Name	Type
@clerk/ui	Patch
@clerk/chrome-extension	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

vercel · 2026-05-04T18:34:08Z

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

Project	Deployment	Actions	Updated (UTC)
clerk-js-sandbox	Ready	Preview, Comment	May 5, 2026 11:11pm

LauraBeatris · 2026-05-05T21:47:22Z

 return;
 }

+ if (noUserExists(this)) {


Added this one that got missed on the first PR

iagodahlem

The declarative shape is great 👏 — I think we still need some improvements to better structure it and separate the wizard responsibilities into more layers, so we can easily extract those components for reuse later, but I think it's good enough as it is for now and we can follow up. Just two small alignment items I'd flag for this PR before the bigger refactor lands as a follow-up:

Flow.Part part= naming convention.
isLoading flowing through ConfigureSSOFlowContext.

iagodahlem · 2026-05-06T10:50:30Z

+ label='Configure'
+ >
+ <ConfigureSSOWizard>
+ {/* TODO: Implement configure steps */}


Suggested change
{/* TODO: Implement configure steps */}

iagodahlem · 2026-05-06T13:10:19Z

+ >
+ <ConfigureSSOFlowProvider
+ enterpriseConnection={enterpriseConnection}
+ isLoading={isLoadingEnterpriseConnections}


I think passing the initial isLoading down to the context and rendering it on the wizard might lead us to issues when invalidating the query, and also for instance, when we start determining the current step after a refresh I think it would be good to have the loading before the wizard even renders, so what do you think of lifting the initial loading state here to ConfigureSSO root? Something like:
constAuthenticatedContent=withCoreUserGuard(()=>{const{ data, isLoading }=__internal_useUserEnterpriseConnections({enabled: true});if(isLoading&&!data){return<FullSpinner/>;}return(// …existing layout…<ConfigureSSOFlowProviderenterpriseConnection={data?.[0]}><ConfigureSSOSteps/></ConfigureSSOFlowProvider>);});
Happy to take this as a separate PR if you'd rather keep this one tight.

iagodahlem · 2026-05-06T13:13:15Z

+
+export const TestConfigurationStep = (): JSX.Element => {
+ return (
+ <Flow.Part part='test-sso'>


I think the convention for Flow.Part part= is camelCase across Sign-In / Sign-Up / SessionTasks / UserVerification (phoneCode2Fa, alternativeMethods, enterpriseConnections, chooseOrganization, etc.). The four other ConfigureSSO steps already follow that — only test-sso here and sso-confirmation in ConfirmationStep are kebab-case.

LauraBeatris self-assigned this May 4, 2026

vercelBotdeployed to Preview May 4, 2026 18:34 View deployment

github-actionsBot added the ui label May 4, 2026

LauraBeatris force-pushed the laura/add-configure-sso-component branch 6 times, most recently from 67fbe0d to bcc4254Compare May 4, 2026 20:09

LauraBeatris force-pushed the laura/add-wizard-to-configure-sso branch from ff61174 to e8b8f9aCompare May 4, 2026 22:14

vercelBotdeployed to Preview May 4, 2026 22:15 View deployment

LauraBeatris force-pushed the laura/add-wizard-to-configure-sso branch from e8b8f9a to 18f5bfdCompare May 4, 2026 22:40

vercelBotdeployed to Preview May 4, 2026 22:41 View deployment

vercelBotdeployed to Preview May 4, 2026 23:40 View deployment

vercelBotdeployed to Preview May 5, 2026 00:51 View deployment

LauraBeatris force-pushed the laura/add-wizard-to-configure-sso branch from 7d5575c to 24fadadCompare May 5, 2026 01:01

vercelBotdeployed to Preview May 5, 2026 01:01 View deployment

LauraBeatris force-pushed the laura/add-wizard-to-configure-sso branch from 24fadad to e4b796eCompare May 5, 2026 01:04

vercelBotdeployed to Preview May 5, 2026 01:05 View deployment

LauraBeatris force-pushed the laura/add-wizard-to-configure-sso branch from e4b796e to 541f9aaCompare May 5, 2026 01:11

vercelBotdeployed to Preview May 5, 2026 01:12 View deployment

LauraBeatris force-pushed the laura/add-wizard-to-configure-sso branch from 541f9aa to b5e2c1aCompare May 5, 2026 01:14

vercelBotdeployed to Preview May 5, 2026 01:14 View deployment

LauraBeatris force-pushed the laura/add-wizard-to-configure-sso branch from b5e2c1a to 0caf48eCompare May 5, 2026 02:16

vercelBotdeployed to Preview May 5, 2026 02:17 View deployment

LauraBeatris force-pushed the laura/add-wizard-to-configure-sso branch from 0caf48e to 1db042bCompare May 5, 2026 02:20

vercelBotdeployed to Preview May 5, 2026 02:21 View deployment

LauraBeatris force-pushed the laura/add-wizard-to-configure-sso branch from 1db042b to 265c4b1Compare May 5, 2026 02:28

LauraBeatris added 6 commits May 5, 2026 18:46

Query for enterprise connections
da46a7c

Add changeset
1a5e8c7

Improve loading state
972d352

Move Wizard to ConfigureSSO folder
029c44f

Update to declarative API
2022081

Add guard for user
a3ab014

LauraBeatris force-pushed the laura/add-wizard-to-configure-sso branch from aa04cf0 to 8c7e926Compare May 5, 2026 21:46

Always display verify domain step
551b23a

LauraBeatris force-pushed the laura/add-wizard-to-configure-sso branch from 8c7e926 to 551b23aCompare May 5, 2026 21:47

LauraBeatris commented May 5, 2026
View reviewed changes

vercelBotdeployed to Preview May 5, 2026 21:48 View deployment

Add element descriptors
78d6cc4

vercelBotdeployed to Preview May 5, 2026 22:01 View deployment

vercelBotdeployed to Preview May 5, 2026 22:14 View deployment

LauraBeatris force-pushed the laura/add-wizard-to-configure-sso branch from 8ff7711 to 17a34d2Compare May 5, 2026 22:20

vercelBotdeployed to Preview May 5, 2026 22:20 View deployment

LauraBeatris force-pushed the laura/add-wizard-to-configure-sso branch from 17a34d2 to a52fec0Compare May 5, 2026 22:43

vercelBotdeployed to Preview May 5, 2026 22:43 View deployment

LauraBeatris force-pushed the laura/add-wizard-to-configure-sso branch from a52fec0 to bb1e4e2Compare May 5, 2026 23:07

vercelBotdeployed to Preview May 5, 2026 23:08 View deployment

Add isCompleted prop to step
a7f1340

LauraBeatris force-pushed the laura/add-wizard-to-configure-sso branch from bb1e4e2 to a7f1340Compare May 5, 2026 23:10

vercelBotdeployed to Preview May 5, 2026 23:11 View deployment

iagodahlem approved these changes May 6, 2026
View reviewed changes

iagodahlem merged commit 763808b into mainMay 6, 2026
43 checks passed

iagodahlem deleted the laura/add-wizard-to-configure-sso branch May 6, 2026 20:25

clerk-cookie mentioned this pull request May 6, 2026
ci(repo): Version packages #8484
Merged

coderabbitaiBot mentioned this pull request May 6, 2026
feat(ui): <ConfigureSSO /> POC #8491
Closed
9 tasks

iagodahlem mentioned this pull request May 7, 2026
chore(ui): Layer architecture for <ConfigureSSO />#8493
Merged
7 tasks

coderabbitaiBot mentioned this pull request May 12, 2026
feat(ui,shared,localizations): provider selection step for <__experimental_ConfigureSSO />#8503
Merged
14 tasks