-
Notifications
You must be signed in to change notification settings - Fork 2
OKO-574 #248
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
base: develop
Are you sure you want to change the base?
OKO-574 #248
Conversation
|
@eldenpark Ready for review |
| import { addStatusRoutes } from "./status"; | ||
| import { makeKeyshareRouter } from "./key_share/v1"; | ||
| import { makeKeyshareV2Router } from "./key_share_v2"; | ||
| import { makeCommitRevealRouter } from "./commit_reveal"; |
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.
Not sure why we would need yet another router. I'll modify
|
@chihunmanse Please review the changes I've made! |
I’ve reviewed the changes |
| router.post("/register", bearerTokenMiddleware, keyshareV2Register); | ||
| router.post( | ||
| "/register", | ||
| commitRevealMiddleware("register"), |
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.
@chihunmanse Question. Why do we need this middleware for almost all route handlers of V2?
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.
@chihunmanse Question. Why do we need this middleware for almost all route handlers of V2?
Because any handler that requires OAuth authentication must ensure the OAuth token was committed and passes reveal validation before executing.
Pull Request
CONTRIBUTING.mdand followed the guidelines.Summary
Links (Issue References, etc, if there's any)