store client-secret as hash only#283
Open
ajgarlag wants to merge 1 commit into
Open
Conversation
ajgarlag
force-pushed
the
stored-client-secret-as-hash
branch
2 times, most recently
from
4e6b1ad to
60c1fe3
Compare
chalasr
requested changes
Jun 16, 2026
chalasr
force-pushed
the
stored-client-secret-as-hash
branch
from
60c1fe3 to
8f9e626
Compare
Collaborator
Author
|
The latest changes look good to me. Thanks for reviewing the UPGRADE wording. I think this PR is ready to merge. |
Member
|
Thank you for this |
ajgarlag
force-pushed
the
stored-client-secret-as-hash
branch
2 times, most recently
from
a49843e to
8ff9146
Compare
ajgarlag
force-pushed
the
stored-client-secret-as-hash
branch
from
8ff9146 to
d0ad780
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Follow up to #273 by @Thomblin (closed by mistake).