New versions of the clients support a new registration flow that also allows enforcing email verification. This is a working implementation of that new API.
The clients implementations are gated behind two feature flags that I have enabled, I've used a web vault compiled from the main branch, but older releases might also work.
Still a draft as I still need to test Invites/emergency access
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.
## 📋 Pull Request Information
**Original PR:** https://github.com/dani-garcia/vaultwarden/pull/5215
**Author:** [@dani-garcia](https://github.com/dani-garcia)
**Created:** 11/21/2024
**Status:** ✅ Merged
**Merged:** 3/17/2025
**Merged by:** [@dani-garcia](https://github.com/dani-garcia)
**Base:** `main` ← **Head:** `register_verify_email`
---
### 📝 Commits (6)
- [`3c7408e`](https://github.com/dani-garcia/vaultwarden/commit/3c7408e21e41407bdf5c991a68a76805eec24393) Implement registration with required verified email
- [`19d4620`](https://github.com/dani-garcia/vaultwarden/commit/19d4620db07d7386f8d2083103151e748e7c82e5) Merge branch 'main' into register_verify_email
- [`efc82da`](https://github.com/dani-garcia/vaultwarden/commit/efc82da5f66d9f99a04c9851d4198b96a5464200) Optional name, emergency access, and signups_allowed
- [`60a9474`](https://github.com/dani-garcia/vaultwarden/commit/60a94740ef14a80556c37a50325389f8ed6ee260) Implement org invite, remove unneeded invite accept
- [`81f5696`](https://github.com/dani-garcia/vaultwarden/commit/81f56966728b2eaa709923bdd09ddf88a220513b) fix invitation logic for new registration flow (#5691)
- [`0eaf43a`](https://github.com/dani-garcia/vaultwarden/commit/0eaf43a7540e575ce0c1e63ec01370656293cbbb) Merge branch 'main' into register_verify_email
### 📊 Changes
**10 files changed** (+260 additions, -19 deletions)
<details>
<summary>View changed files</summary>
📝 `.env.template` (+3 -2)
📝 `src/api/core/accounts.rs` (+95 -13)
📝 `src/api/core/mod.rs` (+3 -0)
📝 `src/api/identity.rs` (+63 -2)
📝 `src/auth.rs` (+32 -0)
📝 `src/config.rs` (+4 -2)
📝 `src/mail.rs` (+21 -0)
➕ `src/static/templates/email/register_verify_email.hbs` (+8 -0)
➕ `src/static/templates/email/register_verify_email.html.hbs` (+24 -0)
📝 `src/static/templates/scss/vaultwarden.scss.hbs` (+7 -0)
</details>
### 📄 Description
New versions of the clients support a new registration flow that also allows enforcing email verification. This is a working implementation of that new API.
The clients implementations are gated behind two feature flags that I have enabled, I've used a web vault compiled from the main branch, but older releases might also work.
Still a draft as I still need to test Invites/emergency access
---
<sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
📋 Pull Request Information
Original PR: https://github.com/dani-garcia/vaultwarden/pull/5215
Author: @dani-garcia
Created: 11/21/2024
Status: ✅ Merged
Merged: 3/17/2025
Merged by: @dani-garcia
Base:
main← Head:register_verify_email📝 Commits (6)
3c7408eImplement registration with required verified email19d4620Merge branch 'main' into register_verify_emailefc82daOptional name, emergency access, and signups_allowed60a9474Implement org invite, remove unneeded invite accept81f5696fix invitation logic for new registration flow (#5691)0eaf43aMerge branch 'main' into register_verify_email📊 Changes
10 files changed (+260 additions, -19 deletions)
View changed files
📝
.env.template(+3 -2)📝
src/api/core/accounts.rs(+95 -13)📝
src/api/core/mod.rs(+3 -0)📝
src/api/identity.rs(+63 -2)📝
src/auth.rs(+32 -0)📝
src/config.rs(+4 -2)📝
src/mail.rs(+21 -0)➕
src/static/templates/email/register_verify_email.hbs(+8 -0)➕
src/static/templates/email/register_verify_email.html.hbs(+24 -0)📝
src/static/templates/scss/vaultwarden.scss.hbs(+7 -0)📄 Description
New versions of the clients support a new registration flow that also allows enforcing email verification. This is a working implementation of that new API.
The clients implementations are gated behind two feature flags that I have enabled, I've used a web vault compiled from the main branch, but older releases might also work.
Still a draft as I still need to test Invites/emergency access
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.