Common change email process

[yurochkoyura]

We want to implement common change email process, it supposed to work as described below:

1. user provides new email
2. we send info to previous email
3. we send veryfication email to new email
4. login with new email is prohibited until it is veryfied
5. once it is veryfied login with previous email is prohibited

The process is very stupid and seems to be very common but we faced with problem implementing it with Fusionauth (FA).
You can use /api/user endpoint and submit new user email but it does not work properly:

1. FA sends email to new address only
2. you are able to login with new email even if you did not verify it
3. after verification you still able to login with previous email.

Any ideas how to implement with no code?

[dan]

@yurochkoyura I can't think of any way to implement this via FusionAuth configuration alone.

Seems like a cool feature request, though. Please consider submitting a feature request and if there's community support, we'll look at putting it into the roadmap: https://github.com/fusionauth/fusionauth-issues/issues

From a scan there, though, it looks like this may be part of this long standing issue: https://github.com/FusionAuth/fusionauth-issues/issues/1

So if you want to add a comment or vote that up, that'd be helpful to us as well.