-
Notifications
You must be signed in to change notification settings - Fork 62
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
Add JWKS support #43
Add JWKS support #43
Conversation
Closes #27
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.
This looks really good! Just a couple minor questions.
I do have one other question. I noticed that the RWMutex is protecting a lot of variables on the backend, minus the oidcStates
because they're a thread-safe cache. And I bet this could be a pretty racy backend IRL, in that it could receive quite a lot of requests in parallel because of its nature.
Do we have any tests explicitly for detecting races? Maybe something like spinning up one backend, then doing a bunch of requests on it in parallel reading and mutating objects, that we could run go's -race
flag on? Would it be worthwhile to do that for this one? Not necessarily in this iteration.
Running concurrency tests is a good idea and something I'm going to put in. |
All comments should be addressed. |
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.
Looks great, just one small optional comment
Closes #27