* /api endpoints only allows requests with application/json Content-Type
Otherwise sends 406 Unacceptable
* Uses CSRF token
The CSRF token is sent as the cookie 'XSRF-TOKEN' on all HTML page
requests. This token is picked up automatically by axios
and sent to the API with all requests as an 'X-XSRF-TOKEN' header.
The middleware runs on all routes and verifies that the token matches
what's stored in the session.
* Re-introduce Email Verification code
Revert "Revert "Email verification""
This reverts commit d154d8bff259350523a0f139e844db96c43d2ee1.
* Uses MJML to generate Reset Password email
* Sends Password Reset and Email Confirmation emails using MJML template
* Sends verified status along with user data
* API endpoint for resending email verification confirmation
* Displays verification status on Account page and allows resending
* Send back error string
* Passes email address through to sign/verify helper
* Uses enum-style object to set verified state
* Sends minimal info when user verifies since it can be done without login
* Provides /verify UI and sends confirmation token to API
* Better name for JWT secret token env var
* Adds mail config variables to Readme
* Encrypts email address in JWT
The JWT sent as the token in the Confirm Password URL
can be unencoded by anyone, although it's signature can only
be verified by us. To ensure that no passwords are leaked,
we encrypt the email address before creating the token.
* Removes unused mail templates
* Resets verified flag when email is changed and sends another email
* Moves email confirmation functions next to each other
* Extracts random token generator to helper
* Moves email confirmation actions into Redux
- updates the AccountForm label with a message to check inbox
- show status when verifying email token
* Uses generated token stored in DB for email confirmation
* Sets email confirmation status to verified if logging in from Github
* Sends email using new method on account creation
* Fixes linting errors
* Removes replyTo config
* Checkbox to toggle project's serveSecure flag
This doesn't yet persist or reload the page.
* Help button that shows modal to explain feature
* Extracts protocol redirection to helper
* Returns promise from saveProject() action to allow chaining
* Setting serveSecure flag on project redirects after saving project
* Set serveSecure on Project model in API and client
* Redirect to correct protocol when project is loaded
* Tries to match user account from list of emails in Github API
Requests the 'user:email' scope from Github which returns the private
emails associated with the user's account.
* Centres GitHub button in layout
* Higher-order component to force some routes to HTTPS
* Force all user-management routes to HTTPS
* Redirect to sourceProtocol as route unmounts.
By default, no redirection occurs if sourceProtocol is not explicitly
defined.
* Sets serveSecure flag on new projects and usea after forcing protocol
The flag is set to `false` on all projects and as the UI has no way to
change this, it always redirects to HTTP after a signup/login action.
* Move HoC to be with other top-level components
* Server should respond to account page request
* Serves AccountView over HTTPS
* Turns HTTPS redirection off in development by default
Will log to the browser console any redirection that would
have happened. Added a line in the README about how to
enable this for testing in development.
* added account page showing username and email
* change username and email
* validate current password and add new password
* reject promise with error for reduxForm submit-validation for current password
* updated user reducer to handle setting sucess and server side async
* warning if there is current password but no new password
* fixes logout button
* import validate function, fixes logout style
* update eslint and dependencies, fix linting errors that can be fixed with --fix
* fix lots of linting errors
* update eslintrc, fix some linting errors
* fix all server side linting errors, untested
* fix errors that fixing linting errors had caused
* fix client side eslint errors
* fix client side linting errors
* fix refs lint errors
* fix more linting errors
* update eslint and dependencies, fix linting errors that can be fixed with --fix
* fix lots of linting errors
* update eslintrc, fix some linting errors
* fix all server side linting errors, untested
* fix errors that fixing linting errors had caused
* fix client side eslint errors
* fix client side linting errors
* fix refs lint errors
* fix more linting errors
* fix some accessibility linting errors
* fix a lot of linting errors
* fix a billion more linting errors
* hopefully fix all linting errors, still need to test
* fix bugs that fixing linting had caused
* Making the email separate for future enhancements
* email-verification added
* Github users are verified
* update package
* Bug fixes and improvements
* jade to pug
* Bug fix
* changed route
* Changed unsaved changes asterisk to an svg circle. #158
* Fixed#100
Unmatched routes are handled by react-router on the client side
and a single wildcard route on server.routes.js renders the index
html.
When the /:username/sketches route is matched and the username is not
valid, the user will be redirected to the index route and a toast
will explain what happened. When the username is 'p5' (default when
logged out) it will show all sketches. Maybe this should be changed
to just public or 'local' sketches?
* Moved unsaved changes SVG to a separate file.
* User not found is now a 404 error.
* Added server rendered 404 page.
* Removed console.log
* 404 Page now renders a random p5 sketch. TODO: make 404 sketches.
* Added 404 header
404 page now fetches a random example sketch
* Moved circle closer to file name
* Render 404 page in SketchList route if !user
