feat: Add send_state
parameter to disable sending of state
#182
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This reverts #181 and adds a
send_state
parameter instead to address #174.According to https://openid.net/specs/openid-connect-core-1_0.html#rfc.section.3.1.2.1,
state
is recommended but not required:In #181 we attempted to make
require_state
skip thestate
verification if it weretrue
, but this was reverted for two reasons:If identity providers make direct requests to the callback phase with a valid token, no
state
is passed in the request. Ifrequire_state
weretrue
, this change fails the request and breaks existing flows.If
state
isn't sent in the first place, it should not be verified.send_state
will now disable the sending of astate
in the authorize phase.