Implement new registration flow with email verification #830

New Issue

MrUnknownDE · 2026-04-05T23:53:39+02:00

MrUnknownDE commented

2026-04-05 23:53:39 +02:00

Originally created by @dani-garcia on 11/21/2024

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

*Originally created by @dani-garcia on 11/21/2024* 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

MrUnknownDE closed this issue

2026-04-05 23:53:39 +02:00

MrUnknownDE referenced this issue

2026-04-06 04:32:18 +02:00

SIGNUPS_ALLOWED with no whitelist [fixes #830] #3112

Sign in to join this conversation.

No Label

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github/vaultwarden#830