Registration email not optional
Steps to reproduce
- Set up registration with "Email is optional" toggle enabled
- Try to register without giving an email
Expected behaviour
The website allows registration to go through
Actual behaviour
A "this field is required" popup appears
Server configuration
Nextcloud version: 25.0.2
That's right, the email is still needed as it's the unique login attribute afterwards. It simply skips the verification where you have to enter a random secret that is emailed to the address.
(sorry for late reply) Could the username not be treated as unique in that situation? I have a mail server connected to the NC user database which provisions accounts for new users, I'd rather them not use an external email in addition to the provisioned one.
I expected "Email is optional" to mean that email can be left empty on registration (or even better: not asked for at all at this stage), and most importantly: mean that the server doesn't need to collect and store this personal data. If "Email is optional" means "Disable email confirmation", it'd probably be better to call it that.
It's concerning (or at least good to be aware of) that the internal design of Nextcloud server requires an email address for each user profile (if I understand correctly). I'd argue an email address should be optional by design and used for specific purposes based on policies and settings.
That's right, the email is still needed as it's the unique login attribute afterwards. It simply skips the verification where you have to enter a random secret that is emailed to the address.
A bit late to the party here, but it seems there's another toggle named "Disable email verification" that only shows up when "Email is optional" is disabled. What does that one do then?
I would also like to give people who do not have an e-mail address or do not wish to provide one the opportunity to register. Unfortunately, this is currently not possible.
Why not possible?
I was able to completely hide the email input process from new users by making a few modifications to this app's source code.
The new registration process I modified is as follows:
- When you press the
Registerbutton on the login page, a form for enteringloginnameandpasswordis displayed immediately without going through the email input process. - Also, there is no
emailinput(pre-filled and disabled) in this form. - Fill out the form and submit. New account registration successful.
loginname is already a unique ID value, so there will be no account conflict issues even if a unique email address is not specified.
since the "Disable email verification" option is already selectable, I see no reason why there shouldn't be an option to completely remove the email requirement from the sign-up process.
I am not yet a contributor to nextcloud. I am willing to submit a pull request after further testing the stability of the modified functionality, but I may have made inappropriate changes to the app's architecture and framework.
So, for now... I just wanted to say that it is fully possible to implement.
Why not possible?
I was able to completely hide the email input process from new users by making a few modifications to this app's source code.
The new registration process I modified is as follows:
- When you press the
Registerbutton on the login page, a form for enteringloginnameandpasswordis displayed immediately without going through the email input process.- Also, there is no
![]()
- Fill out the form and submit. New account registration successful.
loginnameis already a unique ID value, so there will be no account conflict issues even if a unique email address is not specified. since the "Disable email verification" option is already selectable, I see no reason why there shouldn't be an option to completely remove the email requirement from the sign-up process.I am not yet a contributor to nextcloud. I am willing to submit a pull request after further testing the stability of the modified functionality, but I may have made inappropriate changes to the app's architecture and framework.
So, for now... I just wanted to say that it is fully possible to implement.
@smooroodina How is the testing coming along? Any updates on a merge? Thanks!