Unified auth experience

[lovincyrus]

Closes https://github.com/rilldata/rill-private-issues/issues/743

https://www.notion.so/rilldata/Unified-authentication-experience-113ba33c8f578058b2c0f8044b546e0a

https://www.figma.com/design/Qt6EyotCBS3V6O31jVhMQ7/RILL-Latest?node-id=18329-561685&node-type=instance&t=WTfGOxeg7fIZdXaq-0

To review locally: npm run dev -w web-auth
To test in staging: https://ui.rilldata.io

• Trace regression https://github.com/rilldata/rill/commits/main/web-auth/package.json
• Fix cta button rendering in staging auth0
• Rebase after web-auth: use svelte and vite-plugin-singlefile #5965
• test sign up / log in flow in staging
• test last used connection
• modify UI of last used connection
• handle small screen
• FOUT
• https://rilldata.slack.com/archives/C04JP568RR6/p1730160249491529
• fix Unified auth experience #5940

[ericpgreen2]

On staging, when I enter an email address and click "Continue with email", nothing happens.

[lovincyrus]

On staging, when I enter an email address and click "Continue with email", nothing happens.

Try again with Enter to submit password. I'll add the click event to the Continue.

[ericpgreen2]

Can we only designate a sign-in option as "last used" once the user has successfully used it to log-in? See this Jam for two problems:

1. The "last used" parenthetical switches before the next page is loaded
2. I do not complete the Microsoft SSO flow, so I'd consider it "never used" not "last used"

[lovincyrus]

Can we only designate a sign-in option as "last used" once the user has successfully used it to log-in? See this Jam for two problems:

1. The "last used" parenthetical switches before the next page is loaded
2. I do not complete the Microsoft SSO flow, so I'd consider it "never used" not "last used"

Will only set last used in a success callback

To do this the right way, we need to persist it with cookie. See https://github.com/rilldata/rill/blob/main/admin/server/auth/handlers.go#L165

[lovincyrus]

I can remove the last usage implementation in this ref and revisit this

[ericpgreen2]

LGTM. @djbarnwal, since you're closer to this code, can you please also give it a review?

[djbarnwal]

https://jam.dev/c/647b8271-4469-4694-9f53-c0ec127c6b3d
Submitting email doesn't work for me. Tried firefox and chrome.

[ericokuma]

UXQA items:

1. First time logging in or signing up always started with Log in with Email page

We don't want that. We want to show this page instead:

2. auth error of type "invalid_request": the connection was not found

Steps to repro:

• Enter eric.okuma@rilldata.com into email field
• Hit Continue
• See that it says email is SSO-supported
• Hit Continue, get error

@lovincyrus

[lovincyrus]

1. First time logging in or signing up always started with Log in with Email page

This is a bug caused from the latest commit. Will fix

[lovincyrus]

2. auth error of type "invalid_request": the connection was not found

I believe this is expected in staging. I was able to repro this error in the previous staging build.

CleanShot.2024-11-11.at.11.15.51.mp4

[lovincyrus]

Are legacy users allowed to use google or microsoft auth? @djbarnwal Nvm, I just checked the prod rill dash auth pages. The auth options are in there.