[Bug] 401 Error When Adding New User

[Manoj-14]

Summary

Users are encountering a 401 Unauthorized error when attempting to add a new user through the User Management interface.

Description

When submitting the "Add New User" form in the User Management (CRUD Operations) section, the request fails with a status code 401 error. The form appears to accept user input correctly (First Name, Last Name, and Email fields are populated), but the submission fails during processing.

Steps to Reproduce

1. Navigate to the User Management page
2. Fill in the "Add New User" form with the following details:
   • First Name: user
   • Last Name: user
   • Email: user@gmail.com
3. Click the "ADD USER" button
4. Observe the error message: "Error: Request failed with status code 401"

Expected Behavior

The new user should be successfully created and added to the system without any authentication errors.

Actual Behavior

The request fails with a 401 Unauthorized status code, preventing the user from being added to the system.

Error Details

• Status Code: 401 (Unauthorized)
• Error Message: "Request failed with status code 401"
• Form Data:
  • First Name: user
  • Last Name: user
  • Email: user@gmail.com

Possible Causes

• Authentication token expired or missing
• Insufficient permissions for the current user session
• CORS configuration issues
• Backend authentication middleware malfunction
• API endpoint authentication requirements not met

Acceptance Criteria

• Users can successfully add new users without authentication errors
• Appropriate error handling for actual authentication failures
• Proper validation of user input before submission
• Clear error messages that guide users on how to resolve issues

Additional Notes

This appears to be an authentication/authorization issue rather than a validation problem, as the form accepts the input but fails during the API request. Please verify:

1. Authentication token handling in the frontend
2. Backend API endpoint authentication requirements
3. User session management
4. CORS configuration for the API endpoint

[Jaidhuria]

@Manoj-14 assign it to me let me do it

[Manoj-14]

Hey @Jaidhuria, Sure will assign the issue, prior to that i want you to take look at the code and figure out the issue.

[Arpita01-work]

Hey @Manoj-14 , can you assign this task to me, i have prior knowledge related to this problem.

[Jaidhuria]

@Manoj-14 I know how to work on this problem now assign it to me

[Arpita01-work]

Hi @Manoj-14, based on my understanding and the issue details, this seems to be more of an authentication/authorization problem rather than a form or validation issue.

The Add User request is reaching the backend but getting rejected with a 401, which usually happens when the Authorization header (JWT token) is missing, expired, or not being attached correctly from the frontend. Another possibility could be that the logged-in user does not have the required role/permission (for example, ADMIN) to create a new user.

Since a proper 401 response is coming from the backend, CORS can likely be ruled out. It might be worth checking the frontend token handling (axios interceptor / auth header) and the backend security configuration for the Add User endpoint.

Please let me know if I can take a deeper look into the code for this.

[Manoj-14]

@Arpita01-work , will assigning to you.