refactor(core): refactor oidc error response query param #6525
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.
Summary
Introduce a new
parse_error
query parameter flag. The value ofparse_error
can only befalse
.By default, Logto returns the parsed error code and error description in all the
RequestError
error responses. This is to ensure the error responses are consistent and easy to understand.However, when integrating Logto with Google OAuth, the error response body containing
code
will be rejected by Google.code
is considered a reserved OIDC key, and can't be used as the error code key in the error response body.To work around this, we add a new
parse_error
query parameter flag. When parsing the OIDC error body, if theparse_error
is set to false, only oidc error body will be returned.example:
Testing
Test locally
Checklist
.changeset