-
Notifications
You must be signed in to change notification settings - Fork 2.3k
OAuth login options - Login with Google or Discord #1220
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
Comments
I think Github would also be an appropriate login provider for production Puter. I imagine we would have the list of providers as configuration. |
…th 2.0 authentication with Discord and Google to simplify and speed up user access to Puter. This feature provides a seamless alternative to traditional registration, improving both user experience and security.\n\nChanges include:\n- Added OAuth configuration to backend config\n- Created OAuth service and router endpoints\n- Updated database schema to store OAuth user data\n- Added OAuth buttons to login and signup UI\n- Added OAuth provider icons\n\nResolves #1220\n\nai: true
…th 2.0 authentication with Discord and Google to simplify and speed up user access to Puter. This feature provides a seamless alternative to traditional registration, improving both user experience and security.\n\nChanges include:\n- Added OAuth configuration to backend config\n- Created OAuth service and router endpoints\n- Updated database schema to store OAuth user data\n- Added OAuth buttons to login and signup UI\n- Added OAuth provider icons\n\nResolves #1220\n\nai: true
…th 2.0 authentication with Discord and Google to simplify and speed up user access to Puter. This feature provides a seamless alternative to traditional registration, improving both user experience and security.\n\nChanges include:\n- Added OAuth configuration to backend config\n- Created OAuth service and router endpoints\n- Updated database schema to store OAuth user data\n- Added OAuth buttons to login and signup UI\n- Added OAuth provider icons\n\nResolves #1220\n\nai: true
I tried getting AI to do this just to see if it would work; it didn't. However, that PR can serve as a reference for anyone who might want to take this task on. If nothing else, my review comments on it might serve as an example of what not to do. |
I'm sorry it doesn't work, but before you put it in the "not to do", I'll try it myself by making everything open source with documentation. |
@KernelDeimos @DarkCodeStudios |
Hey hello, If you want I can give you my discord username so you can help me, would that be okay? |
Oh - just to clarify, I wasn’t trying to suggest OAuth itself goes in a “not to do” pile! I was only referring to my own attempt in that PR - I asked AI to implement it, and, well… it tried 😅. None of the maintainers will have time to work in this very soon so contribution would be greatly appreciated. |
I would like to propose the implementation of OAuth 2.0 authentication with Discord and Google to simplify and speed up user access to Puter. This feature would provide a seamless alternative to traditional registration, improving both user experience and security.
Motivation
Integrating authentication via Discord and Google would offer several benefits, including:
Increased accessibility: Users can log in with their existing credentials, reducing the need to create a new account.
Enhanced security: Leveraging the advanced security measures provided by Discord and Google reduces the risk of compromised accounts.
Higher user engagement: Users may be more likely to sign up if they can do so quickly with a single click.
Simplified account management: Users could link their Discord or Google accounts to existing Puter accounts, preventing duplicate registrations.
Potential Implementation
Integration of OAuth 2.0 to support authentication with Discord and Google.
Option for users to link their Discord or Google accounts to an existing Puter account.
A clear UI allowing users to choose their preferred authentication method during login/registration.
Optional configuration for administrators to enable or disable specific authentication methods.
Additional Considerations
The implementation could follow security best practices, such as JWT support and refresh tokens, ensuring user data protection. Additionally, this feature could facilitate future integrations with other services.
I hope this proposal can be considered. I am happy to provide further details or contribute to the discussion.
The text was updated successfully, but these errors were encountered: