Summary of login flow.

So I just wanted to summarize the login flow to make it easier for development.

A user is redirected to the login website https://scratch-id.onrender.com/?app_id=123456789&type=external
The user is asked to continue with an existing account, or add a new one
They click "Authorize" which then redirects to the app's callback URL.

So my idea is in order to use ScratchID, website owners must sign up, then create an application, with a callback URL and name.

2. The user is asked to continue with an existing account, or add a new one

I've made a mock up of this:

Sorry I forgot to mention. I made this earlier

This is a much easier system and better, you don't have to accept this:

The user is taken to the login page, they login with comments, cloud etc and then a POST request is sent to the server, the server will store the username, redirect location and more. After user is logged in they will be redirected to their previous site (a url param) with the id of the server response in a param, the site (not the login site, the one before it) will fetch the json from auth-api.beamws.com/oauth/verification/:id

ask chatgpt to summarise this

yeah that’s a good idea

yeah that’s a good idea

With the /verification/:id it will return the username and redirect location and some other stuff

I have a rough start, may you host it with build command npm install and start command npm start

@kRxZykRxZy

@kRxZykRxZy @polylogue2 @snoopythe3-from-scratch, I made one of the UI mockups, do you like it?

Also can you please assign me to the issue?

Also this is what it could look like with Scratch Accounts already added

I think we should remove the what it can do part because a website cant change your account.

…

On Sat, 24 May 2025, 04:19 MyScratchedAccount, ***@***.***> wrote: *Fluffy728* left a comment (ModularGroup/scratch-id#3) <#3 (comment)> Also this is what it could look like with Scratch Accounts already added IMG_0919.jpeg (view on web) <https://github.com/user-attachments/assets/8c73554e-8390-4c92-8de1-e77f3b28f753> — Reply to this email directly, view it on GitHub <#3 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BPVIK2ZN6EXANQYMAHXSD6D277QKZAVCNFSM6AAAAAB5LYIKSWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDSMBWGM2DIMRYGQ> . You are receiving this because you were mentioned.Message ID: ***@***.***>

I think we should remove the what it can do part because a website cant
change your account.
…
It means scopes like in OAuth2, but there will be only one scope - the one to check the account’s username.

Warning: Issues are closed when they are inactive for at least 14 days, and this issue is one of them.

Warning: Issues are closed when they are inactive for at least 14 days, and this issue is one of them.

Not any more

Navigation Menu

Summary of login flow. #3

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Summary of login flow. #3

Description

Activity

snoopythe3-from-scratch commented on May 18, 2025

localpigeons commented on May 18, 2025

kRxZykRxZy commented on May 19, 2025

localpigeons commented on May 19, 2025

kRxZykRxZy commented on May 19, 2025

kRxZykRxZy commented on May 19, 2025

Fluffy728 commented on May 24, 2025

Fluffy728 commented on May 24, 2025

snoopythe3-from-scratch commented on May 24, 2025

Fluffy728 commented on May 24, 2025

github-actions commented on Jun 15, 2025

snoopythe3-from-scratch commented on Jun 15, 2025

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions