Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Client credentials #2323

Closed
ginnavaram opened this issue Apr 3, 2017 · 4 comments
Closed

Client credentials #2323

ginnavaram opened this issue Apr 3, 2017 · 4 comments

Comments

@ginnavaram
Copy link

In OAuth 2 client credentials flow as client secret is almost equivalent to a password should it be encrypted?
Does kong provide any such encryptions?
@Tieske
Copy link
Member

Tieske commented Apr 3, 2017

use ssl?

@ginnavaram
Copy link
Author

ginnavaram commented Apr 3, 2017 •
edited
Loading

Oops sorry I phrased the question incorrectly....I was planning to use ssl but I was thinking more interms of comparing client secret(passed by the client App) with hashed one(hashed using any of the algorithms SHA3 etc) in the datastore.....so that the client secrets are safe in the datastore

@coopr
Copy link
Contributor

coopr commented Apr 3, 2017

I believe this is represented by #1237

@coopr coopr closed this as completed Apr 3, 2017
@ginnavaram
Copy link
Author

are there any plans by Mashape/Kong community in implementing #1237

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@coopr @Tieske @ginnavaram