Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Server error if wrong response_mode is requested #413

Closed
tpazderka opened this issue Aug 24, 2017 · 0 comments
Closed

Server error if wrong response_mode is requested #413

tpazderka opened this issue Aug 24, 2017 · 0 comments
Assignees
@tpazderka
Labels
bug
Milestone
P1: MUST

Comments

@tpazderka
Copy link
Collaborator

When consumer asks for a specific response_mode and this cannot be fulfilled, an error response is produced, but not correctly handled.

Exception Type: TypeError at /oidc/authorization/
--
Exception Value: InvalidRequest('wrong response_mode',) is not JSON seriali=
zable

This should be correctly handled and a proper error response should be returned.
@tpazderka tpazderka added the bug label Aug 24, 2017
@tpazderka tpazderka self-assigned this Aug 24, 2017
tpazderka added a commit that referenced this issue Aug 24, 2017
@tpazderka
Correctly create error response when wrong response_mode requested
e6311a9 
Close #413
@tpazderka tpazderka mentioned this issue Aug 24, 2017
Merged
1 task
tpazderka added a commit that referenced this issue Aug 24, 2017
@tpazderka
Correctly create error response when wrong response_mode requested
6599086 
Close #413
@decentral1se decentral1se added this to the P1: MUST milestone Aug 24, 2017
andrewkrug pushed a commit to mozilla-iam/pyoidc that referenced this issue Jun 6, 2019
@tpazderka @andrewkrug
Correctly create error response when wrong response_mode requested
d692b37 
Close CZ-NIC#413
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@tpazderka tpazderka

Labels
bug
Projects
None yet
Milestone
P1: MUST
Development

No branches or pull requests
2 participants
@decentral1se @tpazderka