Skip to content
This repository has been archived by the owner on Jul 13, 2023. It is now read-only.

InvalidToken exceptions in the schema validator are not caught #530

Closed
jrconlin opened this issue Jul 18, 2016 · 0 comments
Closed

InvalidToken exceptions in the schema validator are not caught #530

jrconlin opened this issue Jul 18, 2016 · 0 comments
Assignees
Labels

Comments

@jrconlin
Copy link
Member

jrconlin commented Jul 18, 2016

They should be caught as they were.

InvalidToken: 
(14 additional frame(s) were not displayed)
...
  File "marshmallow/schema.py", line 767, in _invoke_load_processors
    data=data, many=many, original_data=original_data)
  File "marshmallow/schema.py", line 865, in _invoke_processors
    data = utils.if_none(processor(data), data)
  File "autopush/web/validation.py", line 195, in extract_subscription
    ckey_header=d["ckey_header"],
  File "autopush/settings.py", line 335, in parse_endpoint
    token = self.fernet.decrypt(repad(token).encode('utf8'))
  File "cryptography/fernet.py", line 143, in decrypt
    raise InvalidToken
@bbangert bbangert added this to the PUSHSVC-0: quality milestone Jul 18, 2016
@bbangert bbangert added the bug label Jul 18, 2016
@bbangert bbangert changed the title InvalidToken exceptions in the schema validator are not caught InvalidToken exceptions in the schema validator are not caught Jul 19, 2016
@bbangert bbangert assigned bbangert and unassigned bbangert Jul 19, 2016
@bbangert bbangert self-assigned this Jul 19, 2016
@bbangert bbangert added the p1 label Jul 19, 2016
bbangert added a commit that referenced this issue Jul 19, 2016
bbangert added a commit that referenced this issue Jul 19, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants