Reimplement PKCE to serialize verifier in session #291
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.
Persist code verifier in session information in order to allow HA Jenkins.
Fixes #290 regression: PKCE information was stored in google's AuthorizationCode flow and not serialized into session.
Current google implementation doesn't allow the get/set of verifier code code so, in our case, PKCE can no longer be used from within google flow. Therefore, this change implements PKCE in the plugin.
Testing done
Unit test now verifies PKCE validity instead of presence only.
Change manually tested with Google, with PKCE activated.
Submitter checklist