The spec states that when redirecting back to the client after an authorization request error, the state parameter should be included if it was present in the request:
state
REQUIRED if a "state" parameter was present in the client
authorization request. The exact value received from the
client.
This adds the state parameter to redirect responses for authorization request errors. Additionally this modifies the check_query_values test utility function to inject the state into the expected redirect URI, so that the behaviour is tested.
I think the way I implemented the tests for this change is a little bit hackish. Let me know what you think and if you have any better ideas how it could be implemented. Thanks, Shawn
The spec states that when redirecting back to the client after an authorization request error, the state parameter should be included if it was present in the request:
https://www.rfc-editor.org/rfc/rfc6749.html#section-4.1.2.1
This adds the state parameter to redirect responses for authorization request errors. Additionally this modifies the
check_query_values
test utility function to inject the state into the expected redirect URI, so that the behaviour is tested.Before the change:
After the change:
I think the way I implemented the tests for this change is a little bit hackish. Let me know what you think and if you have any better ideas how it could be implemented. Thanks, Shawn