-
-
Notifications
You must be signed in to change notification settings - Fork 22
Closed
Labels
Milestone
Description
Background
In talking through the "New User Email" flow on 3/22, we identified multiple pieces of New User Registration & Authentication that need to be implemented/changed. One of those pieces is the auth/ endpoint, and configuring django-allauth & potentially installing and configuring django-rest-auth to send confirmation/validation emails to new users upon signup.
One starting place is this blog post by Blake Yang: Django Signup w Activation email via API, although some changes will be necessary for our particular situation. (See issues #111 & #113)
Acceptance Criteria
- Make any necessary changes to the INSTALLED_APPs section of the
base.pyfile inconfig/settingsto wire upallauthand/orrest-auth - Configure/validate a
templatesfolder for email templates inbase.py - Configure an
email backendinbase.pyCookiecutter is currently set up formailhogas a test SMTP server, but we'll need a live server/service for production. - Configure
allauthinbase.py - Add any additional registration URLs to
userauth/urls.py - Add
overrideURL patterns if needed for register, validate, rest password, etc. - Add view logic as needed in
userauth/views.py - Create/Add appropriate
unittestand orpytesttests to cover the above functionality
This Issue Depends On
#111 - Make Email Required on Backend
Open Questions
- See issue [User Registration] JWT Serializer Changes in Support of User Email Validation #113. This issue has the same question around endpoints and naming.