-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
SessionNoAuthTokenAuthentication custom authenticator #53850
Conversation
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## master #53850 +/- ##
=======================================
Coverage 79.52% 79.52%
=======================================
Files 4963 4964 +1
Lines 209669 209733 +64
Branches 35703 35712 +9
=======================================
+ Hits 166737 166799 +62
- Misses 37814 37815 +1
- Partials 5118 5119 +1
|
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 PR is forbidding users from passing in a bearer token to our ApiTokensEndpoint
right? The previous SessionAuthentication
used would just ignore passed tokens I think (feel free to correct me), so does this mean that we now strictly forbid tokens here, and, if a user has an active session and passes a token, we 403 as well?
Legal Boilerplate
Look, I get it. The entity doing business as "Sentry" was incorporated in the State of Delaware in 2015 as Functional Software, Inc. and is gonna need some rights from me in order to utilize my contributions in this here PR. So here's the deal: I retain all rights, title and interest in and to my contributions, and by keeping this boilerplate intact I confirm that Sentry can use, modify, copy, and redistribute my contributions, under Sentry's choice of terms.