BUG: Persisting User Authentication in Redux

[Saksham2k3s]

Description:

New to Redux and encountering a challenge: I need to manage user authentication in my application using Redux. Specifically, I want to store user login information in the Redux state after successful login or registration. Additionally, I aim to ensure that users remain authenticated for a certain period without needing to log in repeatedly.

Steps to Implement:

Locate the relevant files:

• Navigate to the frontend folder of your project.
• Access the src folder.
• Inside src, find the pages folder.
• Look for the Users folder within pages.
• In the Users folder, locate the LoginSignUp.js file, which handles login and sign-up functionality, including Redux integration.

Review Redux architecture:

• Proceed to the redux folder in your project.
• Within the redux folder, find the slice folder.
• The slice folder contains files responsible for managing specific parts of the Redux state.
• Look for the action file that handles user authentication and state management.

Implement authentication logic:

• Open the action file identified in the previous step.
• Implement the necessary logic to store user authentication data in the Redux state after a successful login or registration.
• Consider using Redux actions and reducers to manage user authentication status and related data.
• Ensure that the authentication state persists across the application and remains valid for a defined period, preventing users from needing to log in repeatedly.

By following these steps and implementing the required logic in your Redux action file, you can effectively manage user authentication in your application and ensure a seamless user experience.

[Amrani-Farouk-Hossam-Eddine]

Hi, i'm interesting , can you sign it to me if there is no one currently working on it

[Saksham2k3s]

Yaa sure @Amrani-Farouk-Hossam-Eddine Please help me!

[Amrani-Farouk-Hossam-Eddine]

i want to ask you a question , you have the slices and store of redux what is the problem you are facing exactly so i can understand better

[Saksham2k3s]

We have a file named LoginSignUp.jsx located at /frontend/src/Pages/User. After filling out the login and signup forms, we dispatch the userLogin() function. Upon successful login, we receive user information from the backend, including the user's data and a JWT token. This token is stored on the backend for a specific duration. Once a user is logged in, there is no need to prompt them to login again. The login data should be stored in the state to enable access to other authenticated pages such as the user profile, ordering products, etc.