-
Notifications
You must be signed in to change notification settings - Fork 17
Inactive key fixes #66
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
I've tried to repeat the errors from Travis in my own environment, but failed. Assistance needed by @c00kiemon5ter. |
Fix that updated keys are marked as inactive if we get 304 from server. Make sure we return inactive keys when calling get_jwt_verify_keys().
Signed-off-by: Ivan Kanakarakis <[email protected]>
Signed-off-by: Ivan Kanakarakis <[email protected]>
7f8ff6c
to
33b8070
Compare
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.
Discussion on the comment related to the breaking builds on travis.
Do not merge - we need to cleanup the debug calls.
d494350
to
2ab36b6
Compare
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.
Sorry, but I find the updated = ( ... ) construct extremely unreadable.
Signed-off-by: Ivan Kanakarakis <[email protected]>
Signed-off-by: Ivan Kanakarakis <[email protected]>
Signed-off-by: Ivan Kanakarakis <[email protected]>
2ab36b6
to
54e59e1
Compare
I found two problems when I had the keys stored on a server with caching enabled.
I've supplied two fixes for this together with some updated tests. I'm not 100% sure about the fix for the second problem.