Invalid New-Email Token Causes Traceback

[Julien Funk]

1. Log into SSO
2. Add new email
3. Use the verify email link on the email that appears below
4. Then use the delete link next to the verify link
5. Go to your email box and while still logged into SSO, use the token provided in the email

You should at this point see a backtrace.

[Stuart Metcalfe (stuartmetcalfe)]

We should just detect this case and raise a 404 exception. Set to low priority as the behaviour described would not be expected to work anyway. The issue is merely a difference in the way we report the problem. This is also likely to be a fairly rare occurence.

[Ricardo Kirkner (ricardokirkner)]

Notes to QA:

Follow the steps in the bug description, and instead of getting a traceback you should get a Page Not Found error (404).

[Dave Morley (davmor2)]

I'm getting the ugly debug 404 rather than the nice one. is this just because it's on ec2?

Page not found (404)
Request Method: GET
Request URL: http://ec2-204-236-252-189.compute-1.amazonaws.com/token/spnXq6kWz1B84BH7Q8Xt/+newemail

No EmailAddress matches the given query.

You're seeing this error because you have DEBUG = True in your Django settings file. Change that to False, and Django will display a standard 404 page.

[Dave Morley (davmor2)]

Had a quick chat with Ricardo this is most likely due to it being on ec2 so something to double check on staging/production.

[Dave Morley (davmor2)]

Passes on staging. Results in 404 error from django.