🔐 refactor: Unverified User Verification Logic

[danny-avila]

Summary

I implemented changes to refine the user verification logic, particularly focusing on the handling of unverified emails and user expiration. These modifications enhance the flexibility of our authentication system while maintaining security measures.

• Updated AuthService.js to disable user TTL (Time To Live) when unverified emails are allowed, while still issuing verification emails if email services are enabled.
• Modified the user creation process in registerUser function to consider the ALLOW_UNVERIFIED_EMAIL_LOGIN environment variable when setting the TTL.
• Refactored the localStrategy.js to remove the expiresAt field from existing users if unverified emails are now allowed, ensuring consistency with the new logic.
• Adjusted the email verification check in localStrategy.js to align with the updated unverified email allowance setting.

Testing

To test these changes:

1. Set up different configurations of the ALLOW_UNVERIFIED_EMAIL_LOGIN environment variable.
2. Attempt to register new users and verify that the TTL is set correctly based on the configuration.
3. Test logging in with both verified and unverified email addresses to ensure the system behaves as expected.
4. For existing users, verify that the expiresAt field is removed when logging in if unverified emails are now allowed.

Test Configuration:

• Toggle ALLOW_UNVERIFIED_EMAIL_LOGIN between true and false
• Test with email services both enabled and disabled

Checklist

• My code adheres to this project's style guidelines
• I have performed a self-review of my own code
• I have commented in any complex areas of my code
• My changes do not introduce new warnings
• I have tested the changes with various configurations to ensure proper functionality