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 should consider how accounts will be created when the website is launched. I can think of two ways to do this:
Generate some kind of token (jwt or a simple validation token stored in the DB) and send it in a link to the new member's email. In this implementation, the account information and email would be retrieved from the application. Since we don't have applications yet, we could have a simple endpoint that creates an invalidated account with no password (with permission to do so). A second endpoint is needed to associate the password to the account and validate the token.
Have an endpoint to create a new account (with special permission) with a random password that is sent by email. Later, that person could change their password. This is similar to what we currently have
These are just 2 options, we should further discuss this matter and the options we have
The text was updated successfully, but these errors were encountered:
We should consider how accounts will be created when the website is launched. I can think of two ways to do this:
These are just 2 options, we should further discuss this matter and the options we have
The text was updated successfully, but these errors were encountered: