-
Notifications
You must be signed in to change notification settings - Fork 1.9k
Implements PKCE (Proof Key for Code Exchange) #1407
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
Thanks! This is interesting. I'll need some time to review the RFC to review this PR. |
|
@babariviere Any plans on updating other storage options? I created a fork to implement k8s storage and others (wip) here stpabhi@6c184bb |
|
@stpabhi I plan to implement Redis storage, I may do it this week |
|
I meant etcd and k8s storage options for pkce. I don’t see the code for them in this PR. |
|
Oh sorry, I have misunderstood. I will do it today |
|
@stpabhi it's done if you want to use it |
|
@babariviere thanks, we have already forked dex and implemented pkce internally. I’m interested in getting it done upstream rather than branching out. |
|
I have few suggestions on the PR.
|
|
I will add test later |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks a lot, this is a nice contribution.
The comments inline aside, can we add a test or two? ;)
Update: I've seen this to late
I will add test later
…code_challenge and code_challenge_method
|
What's the status of this PR? Looks like the downstream branch got deleted :/. |
|
Yes, sorry. I have to close the source as they were some code written for my company. |
|
It is sad that this was not merged year (!) ago. As I can see code is still available in this PR. I have mine implementation of PKCE laying around if necessary (if this PR could not be merged for some reason). |
RFC 7636 (https://tools.ietf.org/html/rfc7636)