-
-
Notifications
You must be signed in to change notification settings - Fork 23
make jwt optional inside get_requesting_user without throwing a 500 error
#1213
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?
Conversation
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## develop #1213 +/- ##
===========================================
+ Coverage 85.93% 85.99% +0.05%
===========================================
Files 94 94
Lines 3235 3255 +20
Branches 371 374 +3
===========================================
+ Hits 2780 2799 +19
Misses 380 380
- Partials 75 76 +1 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
Hi @MattShirley - I don't think this is quite what I was after, although I guess it addresses another failure mode. The place where we are currently failing wrt Nebraska is the |
…hirley/handle-optional-jwt
…hirley/handle-optional-jwt
for more information, see https://pre-commit.ci
…-hep/ServiceX into mshirley/handle-optional-jwt
|
@ponyisi I added a no-op/dummy pass through decorator |
Make JWT optional (as already defined in the decorator) inside
get_requesting_userwithout throwing a 500 error.