Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enhancement: Verify email address on registration #1728

Open
1 task done
darkBuddha opened this issue Feb 5, 2024 · 1 comment · May be fixed by #2344
Open
1 task done

Enhancement: Verify email address on registration #1728

darkBuddha opened this issue Feb 5, 2024 · 1 comment · May be fixed by #2344
Assignees
Labels
enhancement New feature or request
Milestone

Comments

@darkBuddha
Copy link
Sponsor

darkBuddha commented Feb 5, 2024

What features would you like to see added?

Email domain restriction has recently been implemented.

But, if ownership of an email address is not verified by e.g. sending a "24h valid token"-link to it, this mechanism can be bypassed by simply entering a random email from the correct domain. There is a high likelihood that the permitted domain will be the 2nd level domain of LibreChat itself and can hence be guessed easily (e.g. gpt.smallbusiness.com -> @smallbusiness.com).

As LibreChat already has mailing functionality for the password reset, maybe it makes sense to add a simple token-based verification to the registration process (1 line email).

Adding this will improve security and allow usage of LibreChat in business environments. Employees with a business email address, that are allowed to register, can not bypass e.g. the daily token limit by creating multiple accounts for bogus email addresses. It also ensures that employees will not find their own email already registered, when they didn't register that account themselves.

There are also legal considerations, as images/files can be uploaded. Files that are illegal to possess/distribute exist. So it should be possible to trace back such cases to the individual user.

More details

Maybe using an env var MAIL_CONF_REQUIRED or similar could make sense, as some people might not need confirmed accounts, or don't have (/ don't want to add) SMTP credentials to their LibreChat instance.

cf. https://blog.bitsrc.io/email-confirmation-with-react-257e5d9de725

Which components are impacted by your request?

General

Pictures

No response

Code of Conduct

  • I agree to follow this project's Code of Conduct
@darkBuddha darkBuddha added the enhancement New feature or request label Feb 5, 2024
@berry-13 berry-13 self-assigned this Apr 6, 2024
@berry-13 berry-13 linked a pull request Apr 6, 2024 that will close this issue
11 tasks
@danny-avila danny-avila added this to the v0.7.3 milestone Apr 16, 2024
@hieronymousch
Copy link

+1 on my end... blocker for me for multiuser

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Status: 🚧 On Going
Development

Successfully merging a pull request may close this issue.

4 participants