feat: Require email verification after signup to restrict access (#371) - #387
Open
Aryanbuha890 wants to merge 13 commits into
Open
feat: Require email verification after signup to restrict access (#371)#387Aryanbuha890 wants to merge 13 commits into
Aryanbuha890 wants to merge 13 commits into
Conversation
|
@Aryanbuha890 is attempting to deploy a commit to the a2521729-9889's projects Team on Vercel. A member of the Team first needs to authorize it. |
Contributor
Author
|
@Muskankr Please review this and check it. |
Owner
|
@Aryanbuha890 , Please resolve CI failing issue as it will cause deployment fail after merge. |
Contributor
Author
@Muskankr Please now see, I resolve the all errors. |
Owner
|
@Aryanbuha890 , Still merge conflicts and ci failing |
Aryanbuha890
force-pushed
the
371-email-verification
branch
from
July 25, 2026 18:31
ad2ed42 to
b8d673d
Compare
Contributor
Author
|
Contributor
Author
|
@Muskankr Please check it these. |
Owner
|
@Aryanbuha890 , resolve conflicts! |
Aryanbuha890
force-pushed
the
371-email-verification
branch
from
July 27, 2026 05:17
361a788 to
4f21d03
Compare
Owner
|
@Aryanbuha890 , Still merge conflicts |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

Description
This PR resolves #371 by adding an email verification step after user signup. Logged-in users who are not yet verified will have restricted access until they verify their email.
Changes Made
1. Database & Model Changes
UserProfilemodel containing anis_verifiedboolean field (linked one-to-one with standard User).post_savereceiver to automatically create user profiles for new signups.0006_userprofile.2. Backend Views & Endpoint Verification
SignupSerializerto require a unique email on registration.TokenObtainPairSerializerto return verification claims inside login tokens and responses.signupview to sign a verification token (using DjangoTimestampSigner) and output/send the link.3. Frontend States & Dashboard UX
useAuth.tsto manage email registration parameters and handle periodic status verification polling.emailfield insideAuthModal.tsxduring signup.VerifyEmailPage.tsxto process the cryptographically signed token and output success/failure feedback.Verification Results
Ran 27 tests in 12.162s OK