I am using the community version of FusionAuth 1.25 and when setting up self registration I am choosing to log in with username and to verify registration. Since I am using logging in with username it doesn't let a person enter an email when registering. How does it verify then? I think password and username required during registration should be automatic but I don't see that option or am I missing a step? Thanks.
A user could have a separate email address. For example:
- user signs up for application a, which takes an email address and a password
- user then signs up for application b, which takes a username and password, but has email verification enabled
If that isn't the case, you shouldn't enable email verification, since FusionAuth will have no way of sending the email .
Does that help?
Is there a way to have username, email and password for registration without buying a Reactor license or creating my own login form? Startup project with no budget leaves me with few options. Thanks!
Nope, I think you've outlined the two options I'd recommend:
- build your own if you are money constrained
- use a license and the developer license if you are time constrained
Do note that there is a free trial for the developer license if you want to kick the tires and make sure that it solves your needs.
Finally, is there a reason you can't let users login with an email address?
They can (and I prefer) to have them login with an email address. We use the username to differentiate and display the user without exposing their email address.
We only take the username, email and password to register. I was hoping to use as much of your prebuilt objects as possible without creating our own. No worries as that is what I will do. Thanks for your feedback!
Ah, thanks, that makes sense.
Each application can have a username (in the registration object). That username can't be used to login, but it can be used for display purposes in your application: https://fusionauth.io/docs/v1/tech/apis/registrations/
You could allow people to register/login with email address/password and then let them choose their
registration.usernamefor use in the application (you'd have to build a page with a form that would use an API key to let them do so). Now that I think about it, I guess you could do the same with
user.username, which is the username they can log in with. So that might be an option.
Anyway, good luck and let us know how things go!