User service

[SirOphis]

Central hub for secure authentication, user management, and access control. This service is an integral part of our microservices architecture, designed to provide a seamless and secure experience for users interacting with the jscheduler platform.

USER DATA MODEL:

• Id: Unique identifier for each user.
• Username: Chosen username for the application.
• Email: Email address for communication purposes.
• Password: Securely hashed and salted password for authentication.
• FirstName: User's first name.
• LastName: User's last name.
• Birthdate: User's date of birth.
• TokenExpired: Expiry timestamp for the user's JWT.
• SetOfRoles: Collection of roles assigned to the user.

ROLE DATA MODEL:

• Id: Unique identifier for each role.
• Name: Role's name.
• UserList: List of users assigned to the role.
• Privileges: List of privileges associated with the role.

PRIVILEGE DATA MODEL:

• Id: Unique identifier for each privilege.
• Name: Privilege's name.
• Roles: List of roles that have the privilege.

USER SPEC:

Login:

1. Users can securely sign in using their email and password or through OAuth2 authentication with platforms like Facebook or Gmail.
2. Passwords are hashed and salted using strong encryption algorithms to protect user information.
3. Upon successful authentication, users are assigned their respective roles to access the application securely.

Sign Up:

1. Users provide necessary information, including username, email, password, first name, last name, and birthdate. Alternatively, information can be retrieved from connected accounts like Google.
2. Implement robust data validation to ensure accuracy and completeness.
3. Users are assigned a default role, such as "User." Additional roles like 'Administrator' and 'Editor' can be assigned by an administrator.
4. An email verification is sent to the user for confirmation after signing up.
5. Users must verify their accounts before gaining full access to the application.

Password Recovery:

1. Users who forget their passwords can enter their email address.
2. A secure code along with a provisional password is sent to the user's email, allowing them to log in.
3. Users are prompted to change their password immediately upon logging in for enhanced security.

ADDITIONAL CONSIDERATIONS:

Security Enhancements:

• Implement multi-factor authentication (MFA) for an additional layer of security.
• Regularly update and patch dependencies to address potential security vulnerabilities.

API Rate Limiting:

• Implement rate limiting to prevent abuse and enhance security against brute force attacks.

Logging and Monitoring:

• Implement comprehensive logging for user actions and system events.
• Set up monitoring to detect and respond to suspicious activities.

User Profile Customization:

• Consider allowing users to customize their profiles with additional information, such as profile pictures or bio.

Localization:

• Support multiple languages for a more inclusive user experience.