User Authentication: Introducing Login/Sign-up Functionality #10
Comments
|
No its not good for this project
…On Fri, 10 May 2024 at 5:22 PM, SAMARTH BAHIRGONDE ***@***.***> wrote:
As our open-source chat application gains traction among users, it's
crucial to prioritize the implementation of a robust authentication system.
Introducing login and sign-up functionality not only enhances user
experience but also bolsters security measures. By enabling users to create
accounts and authenticate themselves securely, we can personalize their
experience, facilitate user engagement, and ensure data privacy.
*Objective:*
The primary objective of this enhancement is to integrate a user
authentication system into our open-source chat application. This includes
implementing features such as user registration, login, password
management, and session handling.
*Key Features:*
1. User Registration: Allow users to create new accounts by providing
essential details such as username, email, and password.
2. Login: Enable registered users to authenticate themselves securely
using their credentials.
3. Password Management: Implement password encryption and provide
options for password reset and recovery.
4. Session Handling: Maintain user sessions securely to ensure
seamless navigation within the application.
5. Security Measures: Implement robust security measures such as
encryption, hashing, and protection against common vulnerabilities like SQL
injection and cross-site scripting (XSS).
—
Reply to this email directly, view it on GitHub
<#10>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AXH6TTUEI44TCAI3LYWDUZLZBSYHZAVCNFSM6AAAAABHQP2RJCVHI2DSMVQWIX3LMV43ASLTON2WKOZSGI4DSNJYGU3TGOI>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
|
Hey! @urstrulynishkarsh I'm excited to contribute to the project by implementing the login and signup functionality. Here are the two approaches we can follow to implement the authentication part :
Let me know your thoughts on this approach! Also, I have worked on socket.io and have a good experience of handling such backend portions. I am eager to work and contribute on this project. Can you assign this issue to me? GSSC'24 |
|
Hey ashutosh but our aim that we don’t want to store any information of user
…On Fri, 10 May 2024 at 5:54 PM, Ashutowsh ***@***.***> wrote:
Hey! @urstrulynishkarsh <https://github.com/urstrulynishkarsh> I'm
excited to contribute to the project by implementing the login and signup
functionality.
Here are the two approaches we can follow to implement the authentication
part :
1.
Authentication using Appwrite or Firebase
We can directly make use of these backend services for authentication
2.
Authentication using custom logins/registration using JSON Web Tokens
(JWT) :
Another method we could explore is implementing custom login and
registration using JSON Web Tokens (JWT). With JWT, we can securely manage
user authentication without relying on third-party services. This approach
offers flexibility and control over user authentication processes while
maintaining security standards.
Let me know your thoughts on this approach!
Also, I have worked on socket.io and have a good experience of handling
such backend portions. I am eager to work and contribute on this project.
Can you assign this issue to me?
—
Reply to this email directly, view it on GitHub
<#10 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AXH6TTUFN6GPEVIHJ6RKCGLZBS4BTAVCNFSM6AAAAABHQP2RJCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMBUGUYTQMBVGE>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
But chat app have to provide feature show chat history and authentic user for conversation for that user data is necessary |
|
So, @urstrulynishkarsh can you brief us about the requirements and specifications needed to contribute into authentication part for this application. |
|
👋 Hello! I'd be happy to help with this issue. Could you please assign it to me? Additionally, could you please label it for the appropriate level? Thank you! 🚀 |
|
@urstrulynishkarsh I think it's better to add this feature to our project. What do you think? |
|
No it’s not a good feature
…On Sat, 11 May 2024 at 12:09 AM, asr2003 ***@***.***> wrote:
@urstrulynishkarsh <https://github.com/urstrulynishkarsh> I think it's
better to add this feature to our project. What do you think?
—
Reply to this email directly, view it on GitHub
<#10 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AXH6TTSRDPEPNK7DQMWDQIDZBUH5JAVCNFSM6AAAAABHQP2RJCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMBVGA4TINBQGQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
Closing. It isn't the part of project roadmap. Thanks @sammy429b for suggesting this feature :) |
As our open-source chat application gains traction among users, it's crucial to prioritize the implementation of a robust authentication system. Introducing login and sign-up functionality not only enhances user experience but also bolsters security measures. By enabling users to create accounts and authenticate themselves securely, we can personalize their experience, facilitate user engagement, and ensure data privacy.
Objective:
The primary objective of this enhancement is to integrate a user authentication system into our open-source chat application. This includes implementing features such as user registration, login, password management, and session handling.
Key Features:
The text was updated successfully, but these errors were encountered: