New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Satellite signup: Update activation flow #6428
Comments
mobyvb
added
Needs Estimation
Issue still needs story pointing
and removed
Needs Estimation
Issue still needs story pointing
labels
Oct 18, 2023
mobyvb
changed the title
Investigation: activation improvements
Satellite signup: Update activation flow
Nov 7, 2023
Change satellite/db: add activation_code column mentions this issue. |
Change satellite/{console,web}: add activation code config flag mentions this issue. |
Change satellite/{console,emails}: add activation code email mentions this issue. |
Change satellite/console: implement account activation with code mentions this issue. |
Change web/satellite: implement account activation with code mentions this issue. |
storjBuildBot
pushed a commit
that referenced
this issue
Nov 22, 2023
This change adds a new column to the user table, which will hold a random code for account activation. And another to hold the signup request ID as another layer of verification. Issue: #6428 Change-Id: Icd46cb5d8fc76102264d599aca27686cd8b2e84e
storjBuildBot
pushed a commit
that referenced
this issue
Nov 22, 2023
This change adds a config flag for whether signup activation code should be used. Issue: #6428 Change-Id: I2b2b1e76f6013eab6438aefba848af0a4bd62544
storjBuildBot
pushed a commit
that referenced
this issue
Nov 22, 2023
This change adds an email template for sending activation codes. Issue: #6428 Change-Id: Ief56a2e32ac0a335561572b9573215da24d9146b
andriikotko
pushed a commit
that referenced
this issue
Nov 28, 2023
This change adds a config flag for whether signup activation code should be used. Issue: #6428 Change-Id: I2b2b1e76f6013eab6438aefba848af0a4bd62544
andriikotko
pushed a commit
that referenced
this issue
Nov 28, 2023
This change adds a config flag for whether signup activation code should be used. Issue: #6428 Change-Id: I2b2b1e76f6013eab6438aefba848af0a4bd62544
storjBuildBot
pushed a commit
that referenced
this issue
Nov 29, 2023
This change implements account activation using OTP code. Based on whether this activation method is activated, signup will generate a 6-digit code and send it via email. A new endpoint is added to validate this code and activate the user's account and log them in. Issue: #6428 Change-Id: Ia78bb123258021bce78ab9e98dce2c900328057a
storjBuildBot
pushed a commit
that referenced
this issue
Nov 29, 2023
This change implements account activation using OTP code. Based on whether this activation method is activated, signup will require the user to fill the activation code to activate their account. Issue: #6428 Change-Id: Ifdd3e34ddb8ab299dd24b183f9c484613b2e8888
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Implement a new email verification method that makes use of a 6-digit emailed code rather than an activation link.
Because this feature makes significant changes to common workflows, we should implement it with a feature flag, so that we can easily switch between link-based email verification and one-time-code-based email verification.
AC:
The text was updated successfully, but these errors were encountered: