Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Auth Design #4

Open
samuraikun opened this issue Nov 11, 2023 · 3 comments
Open

Auth Design #4

samuraikun opened this issue Nov 11, 2023 · 3 comments
Assignees

Comments

@samuraikun
Copy link
Collaborator

samuraikun commented Nov 11, 2023

Authentication/Authorization

Reason

Flow

sequenceDiagram
    participant User
    participant Next.js App (Vercel)
    participant Supabase Auth (OAuth)
    participant Cloud Run

    User->>Next.js App (Vercel): Enter Login Information
    Next.js App (Vercel)->>Supabase Auth (OAuth): Authenticate using Google Account
    Supabase Auth (OAuth)-->>Next.js App (Vercel): Authentication Token
    Next.js App (Vercel)->>Cloud Run: Request with Auth Token
    Cloud Run->>Supabase Auth (OAuth): Verify Token
    Supabase Auth (OAuth)-->>Cloud Run: Verification Result
    Cloud Run->>Next.js App (Vercel): Response
    Next.js App (Vercel)-->>User: Display Response
Loading
@Yo-mah-Ya
Copy link
Collaborator

@samuraikun
Want some explicit comments where and how exactly we store user password just in case.
And token as well.

@samuraikun
Copy link
Collaborator Author

@samuraikun Want some explicit comments where and how exactly we store user password just in case. And token as well.

Supabase supports most of the processes required for authentication.
We don't need to manage passwords and tokens by ourselves.
https://supabase.com/docs/guides/auth

@Yo-mah-Ya
Copy link
Collaborator

Great !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants