You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We've had a customer ask for a "Forgot username" workflow to the hosted login pages.
The use case is as follows:
The customer has many legacy users that have traditionally used usernames to login.
The user's do have a phone or email address.
Even though you could log in with email, in practice, forgetting a username likely results in a call to the support desk.
Since this does not exist in the product, they have had to build it.
In practice, the username may be a username, or it could be an account number.
The ideal solution for this customer would be:
Add the ability to add a link to the login page or the registration page - named "Forgot username".
This may mean we write the feature, and the themed page but by default maybe we don't display it, but it could be added to an advanced theme, or turned on by a theme policy or an application policy.
The themed page would collect an loginId of email, phoneNumber or some verifiable identity that we would allow us to send something to the user.
We could accept this input and look up the user, if they have a primary username we would send an email to the user. This would be a terminal operation.
We could optionally send all usernames in the email if the user has more than one defined.
Add Forgot Username to themed pages
Description
We've had a customer ask for a "Forgot username" workflow to the hosted login pages.
The use case is as follows:
In practice, the username may be a username, or it could be an account number.
The ideal solution for this customer would be:
loginId
ofemail
,phoneNumber
or some verifiable identity that we would allow us to send something to the user.username
we would send an email to the user. This would be a terminal operation.Community guidelines
All issues filed in this repository must abide by the FusionAuth community guidelines.
The text was updated successfully, but these errors were encountered: