feat: save pkce code verifier/challenge for debugging #1455
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.
In
oidcProvider.js
, persist to localStorage the values of the last used PKCEcode_verifier
andcode_challenge
. This might help in debugging esoteric issues as reported in #1440.The last used values can be found using DevTools or a JS console to view localStorage items
last-code-verifier
andlast-code-challenge
. Thelast-code-challenge
should be the URL encoded Base64 representation of the SHA256 digest oflast-code-verifier
.In a Linux shell, the proper code challenge for a given
last-code-verifier
can be calculated by invoking: