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.

Sign up for GitHub

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

Jump to bottom

Why does logging in through oauth always create a new user instead of binding an existing user? #4237

Open
zhimibuwudn opened this issue Dec 28, 2024 · 0 comments
Open

Why does logging in through oauth always create a new user instead of binding an existing user? #4237

zhimibuwudn opened this issue Dec 28, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@zhimibuwudn
Copy link

zhimibuwudn commented Dec 28, 2024 •
edited
Loading

Describe the bug

Why does logging in through oauth always create a new user instead of binding an existing user? For example, I want to use the mailbox as an identifier when oauth logs in, if the mailbox exists, how to bind an existing account?

Steps to reproduce

Why does logging in through oauth always create a new user instead of binding an existing user?

The version of Memos you're using

Version: v0.23.0

Screenshots or additional context

No response
@zhimibuwudn zhimibuwudn added the bug Something isn't working label Dec 28, 2024
@zhimibuwudn zhimibuwudn changed the title Why do you always create new users through single sign-on instead of binding existing users? Why does logging in through oauth always create a new user instead of binding an existing user? Dec 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@zhimibuwudn